datadog

Datadog through One

|.

One exposes Datadog through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform datadog if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Datadog is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.

Before a write

Creates, updates, deletes and sends land on a real Datadog account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.

Actions

Cases

Action	Method	Path	Action id
Get a Case’s Details	GET	/api/v2/cases/{{caseId}}	conn_mod_def::GJ2NJ5wh_Hk::hVdjXRrnRQufONtadt3LVw
Search Cases	GET	/api/v2/cases	conn_mod_def::GJ2NKw09SuI::6Cgi1gFUR1mr8QFRTjC8kw
Archive a Case	POST	/api/v2/cases/{{caseId}}/archive	conn_mod_def::GJ2NHwfoe8c::34WNqmJNSfuITikDbz5dPw
Assign a Case	POST	/api/v2/cases/{{caseId}}/assign	conn_mod_def::GJ2NH4_52I8::h_B-CGS7SVW5vOF1ZhzSgQ
Comment on a Case	POST	/api/v2/cases/{{caseId}}/comment	conn_mod_def::GJ2NIBeJu58::h5mD8ScpQG2vB4KJOe4AcQ
Create a Case	POST	/api/v2/cases	conn_mod_def::GJ2NIKb-e5g::pL8gHPO_T0ydOMJw7t99xw
Delete a Case Custom Attribute	DELETE	/api/v2/cases/{{caseId}}/custom_attributes/{{customAttributeKey}}	conn_mod_def::GJ2NJeFL7Yc::bWA-qGUoT_ic2IgZ8X5tpQ
Link an Existing Jira Issue to a Case	PATCH	/api/v2/cases/{{caseId}}/relationships/jira_issues	conn_mod_def::GJ2NKKx2gyc::9KDUFHEPTSOVkJPyk7MLWw
Link an Incident to a Case	POST	/api/v2/cases/{{caseId}}/relationships/incidents	conn_mod_def::GJ2NKUFlLuE::MfgjVCA4Q1GOfBbHT40Tdw
Remove a Case’s Jira Issue Link	DELETE	/api/v2/cases/{{caseId}}/relationships/jira_issues	conn_mod_def::GJ2NKoR2c-Y::kDYBwvUzRlGZkhr0mUOA-A
Unarchive a Case	POST	/api/v2/cases/{{caseId}}/unarchive	conn_mod_def::GJ2NK5hI8-8::mjoufApTR8mnjcVADS7lTw
Unassign a Case	POST	/api/v2/cases/{{caseId}}/unassign	conn_mod_def::GJ2NLEs_fxE::Ua9_szZhQvyf-hfLsp4uEA