Skip to main content
Glama

List takedowns

list_takedowns
Read-only

List takedowns: self-guided enforcement attempts the user works against matches (notolens never submits anything itself). state picks the open queue (the default) or the closed history; each item links back to its match, and get_takedown shows the full timeline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_takedowns"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. Page size is 50.
stateNoWhich bucket to list: open attempts in progress (default) or closed ones.
monitor_idNoLimits results to one monitor.

Output Schema

NameRequiredDescriptionDefault
openYes
pageYes
totalYes
closedYes
page_sizeYes
takedownsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / takedowns / items / properties / match / properties / kind / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / takedowns / items / properties / attempt / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +"number"
  3. Changed1 schema field changed
    • changedInput schema / properties / monitor_id / description
      Previous value: -"Restrict to one monitor."New value: +"Limits results to one monitor."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, so safety is covered. The description adds genuinely non-obvious domain behavior: that these are user-driven attempts and the service never submits anything on its own, plus that each returned item links back to its match. Return-shape detail is left to the output schema, which is appropriate.

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?

Two sentences, front-loaded with the resource and the critical 'never submits anything itself' clarification before the parameter and sibling guidance. Dense but every clause carries information; only the parenthetical stacks two ideas in one breath.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and all three parameters are schema-documented. The remaining minor gap is that per-monitor listing behavior (monitor_id) is never acknowledged in prose, though nothing critical is missing for a correct call.

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 description coverage is 100%, so the schema fully documents page, state, and monitor_id. The description restates the state semantics (open default vs closed history) which the schema already says, and says nothing about page size or monitor_id filtering — this is baseline territory.

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+resource ('List takedowns') and immediately defines what a takedown is in this domain — self-guided enforcement attempts the user works against matches, with notolens never submitting anything itself. That definition alone separates it from get_takedown and from send-style siblings.

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

Usage Guidelines4/5

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

'state picks the open queue (the default) or the closed history' tells the agent which bucket to request, and 'get_takedown shows the full timeline' routes the agent to the detail tool when per-item history is needed. There is no explicit exclusion for monitor-scoped listing or paging, but the core use/alternative decision is covered.

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