overlay: 1.0.0
info:
  title: API Evangelist Logs surface overlay (Datadog)
  version: 1.0.0
extends: openapi/datadog-logs-api-openapi.yml
x-generated: '2026-09-23'
x-method: generated
x-source: openapi/datadog-logs-api-openapi.yml
x-rationale: >-
  Add MCP tool bindings and workflow / skill pointers to the Logs v2 surface
  (SubmitLog + ListLogs). Does not mutate the underlying spec.
actions:
  - target: $.info
    description: Attach MCP + workflow pointers to info.
    update:
      x-mcp-tools:
        - {tool: search_datadog_logs, toolset: core, binding: rest, backs: [ListLogs]}
        - {tool: analyze_datadog_logs, toolset: core, binding: rest, backs: [AggregateLogs]}
      x-arazzo-workflows:
        - ../arazzo/datadog-ingest-and-search-logs-workflow.yml
        - ../arazzo/datadog-create-log-archive-workflow.yml
        - ../arazzo/datadog-create-log-pipeline-workflow.yml
        - ../arazzo/datadog-create-log-metric-workflow.yml
      x-agent-skill: skills/datadog-ingest-and-search-logs.md
  - target: "$.paths['/api/v2/logs'].post"
    description: Note the intake vs read-side split.
    update:
      x-agent-guidance: >-
        SubmitLog writes to the log INTAKE endpoint (https://http-intake.logs.<site>).
        The read side (ListLogs / search) lives on the api. host. Agents that
        ingest logs must not assume the same host for both operations.