Skip to main content
Glama

Start takedown

start_takedown
DestructiveIdempotent

Start a self-guided takedown on a match: opens an enforcement attempt the user works through manually, using the match's possible next steps as the guide; notolens never submits or sends anything itself. Requires an open match (inbox or watching); a closed match errors. Starting moves the match to in_takedown and, except for a search ad, arms recurring record refreshes so a subject that stays up keeps being probed; it stays in_takedown until the attempt closes or the match is resolved or dismissed. Safe to repeat: an already-open takedown is returned with created=false. add_takedown_event records work performed, update_takedown closes the attempt, and get_match_evidence provides the PDF to attach when filing.

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": {
      "match_id": "<match_id>"
    },
    "name": "start_takedown"
  }
}

Input Schema

NameRequiredDescriptionDefault
match_idYesMatch id from list_matches.

Output Schema

NameRequiredDescriptionDefault
createdYes
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.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing state transitions (match moves to in_takedown until the attempt closes or the match is resolved/dismissed), a side effect the annotations never hint at (recurring record refreshes, except for search ads), and the important scope limit that notolens never submits or sends anything itself. The idempotency claim is consistent with idempotentHint=true, and the write/mutation framing is consistent with destructiveHint=false being absent here (destructive is true).

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-loaded with the core action, and each subsequent clause carries distinct information (precondition, state effect, idempotency, related tools). It is dense and semicolon-chained, which makes it slightly harder to scan than a shorter structured form, but nothing is redundant.

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?

For a single-parameter mutation with real side effects, the description covers prerequisites, error behavior, state transition, refresh behavior, idempotency, and the follow-on tools in the workflow. With an output schema present, no return-value explanation is needed.

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 single match_id parameter is fully documented in the schema, so the baseline is 3. The description implies the match must be in inbox or watching state but adds no syntax or sourcing detail beyond the schema's "Match id from list_matches."

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?

Specific verb and resource ("Start a self-guided takedown on a match") immediately qualified by what that actually means: opens a manual enforcement attempt guided by the match's next steps. It is clearly distinguishable from add_takedown_event and update_takedown, which it names with their distinct roles.

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?

Explicit preconditions ("Requires an open match (inbox or watching); a closed match errors") and explicit repeat-call semantics (already-open takedown returns created=false). It also routes the agent onward: add_takedown_event records work, update_takedown closes, get_match_evidence supplies the PDF to attach.

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