Skip to main content
Glama

Update takedown

update_takedown
DestructiveIdempotent

Change a takedown's status. succeeded (the subject is down; resolves the match), unsuccessful (tried and failed) or dropped (abandoned) close an open attempt; both non-success closes return the match to inbox for fresh triage and stop its recurring checks. open reopens the latest closed attempt, moving the match back to in_takedown and re-arming its check (search ads take none); reopening fails when a newer attempt exists or the subject reappeared after it closed, and start_takedown opens a fresh attempt instead.

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": {
      "takedown_id": "<takedown_id>",
      "status": "<status>"
    },
    "name": "update_takedown"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status: open reopens a closed attempt; succeeded, unsuccessful or dropped close an open one.
takedown_idYesTakedown id from list_takedowns.

Output Schema

NameRequiredDescriptionDefault
takedownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / takedown / properties / attempt / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +"number"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructive/idempotent annotations by disclosing downstream effects: non-success closes return the match to inbox and stop recurring checks, while reopening moves the match to in_takedown and re-arms its check. It further documents precondition failures and the fallback path, which the annotations cannot express.

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

Conciseness4/5

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

Front-loads the core action, then groups semantics by status family (closing vs. reopening) in a logical order with no filler. The reopening clause is long and runs several conditions together, which slightly hurts scannability but every clause carries operational information.

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

Completeness5/5

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

Given only two required parameters, full schema coverage, and the presence of an output schema, the description covers everything an agent needs: what each status does to the match, what breaks, and which sibling to use instead. No meaningful gap remains.

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

Parameters4/5

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

Schema coverage is 100% and the status enum is already documented in the schema, so the baseline is 3. The description nonetheless adds real meaning by spelling out the state transitions, side effects, and preconditions attached to each enum value, and identifies takedown_id context implicitly through the reopen/close flow.

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

Purpose5/5

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

States a specific verb and resource ("Change a takedown's status") and then enumerates the four statuses with their meanings, so the agent knows exactly what the operation does. It also names the sibling start_takedown as the alternative for a related intent, distinguishing itself from it.

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

Usage Guidelines5/5

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

Explains precisely when each status value applies: succeeded/unsuccessful/dropped close an open attempt, open reopens the latest closed attempt. It also gives explicit exclusions and failure conditions ("search ads take none", reopening fails when a newer attempt exists or the subject reappeared) and routes to start_takedown for a fresh attempt.

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.

Resources