Skip to main content
Glama

Ads Uploader: Meta Ads MCP

Cancel Job

ads_cancel_job
DestructiveIdempotent

Cancel a running ad creation job or media ingest job.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobId": "<jobId>"
    },
    "name": "ads_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesAd creation job ID or media ingest job ID (ingest_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and idempotentHint=true, so the risk profile is covered. The description adds the useful constraint that only running jobs are targeted, but is silent on what happens to a job that is already complete or on any partial artifacts left behind.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no filler, and the operative verb leads. There is nothing to trim and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter cancel tool with full annotations and no output schema, most of what an agent needs is present. It still lacks any statement of outcome or failure behavior, which matters for a destructive operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the jobId property already documents that it accepts either an ad creation job ID or an ingest_... ID. The description adds no syntax, format, or validation detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Cancel') and resource ('a running ad creation job or media ingest job'), and names the two job families it applies to. It does not distinguish itself from the sibling ads_edit_cancel, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'running' implies a precondition, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as ads_edit_cancel or ads_get_job for inspecting a job instead of cancelling it. The agent must infer the selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.