Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Stop scraping

stop_audience_scrape
DestructiveIdempotent

Stops an ongoing audience scrape job by ID and marks that audience as COMPLETE, halting further data collection.

Instructions

Stop scraping. Required API key scope: audiences:write. DELETE /audiences/{id}/scrape Signals the scrape job to stop and marks the audience COMPLETE.

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": {
      "id": "<id>"
    },
    "name": "stop_audience_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds real context beyond annotations: the required API key scope (audiences:write), the HTTP method and path (DELETE /audiences/{id}/scrape), and the terminal state change to COMPLETE, which is not expressed anywhere in the annotations. It does not clarify whether the stop is asynchronous or whether partially scraped members are retained, which matters given destructiveHint=true.

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?

Four short, front-loaded lines with zero filler: name, auth scope, endpoint, effect. Every line carries information an agent needs before calling.

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?

For a single-parameter mutation with no output schema, the definition covers purpose, auth scope, endpoint, and resulting state. The only gap is outcome detail — whether the call returns immediately vs. awaiting the job to settle, and whether any scraped data is discarded.

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% but the schema only says 'Path parameter `id`.' with no indication of which entity it identifies. The description's DELETE /audiences/{id}/scrape line disambiguates that the id is the audience id, not a scrape job id — a genuine addition over the schema.

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?

States a specific verb and resource ('Stop scraping') and then defines the exact effect: signals the job to stop and marks the audience COMPLETE. It is clearly the counterpart to start_audience_scrape, though it never names that sibling explicitly, so sibling differentiation is by name convention rather than stated contrast.

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

Usage Guidelines3/5

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

Usage is implied by the name and the 'signals the scrape job to stop' phrasing — you call this on a running scrape for a given audience. There is no explicit when-to-use guidance, no statement about what happens if no scrape is in flight, and no pointer to start_audience_scrape as the inverse operation.

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

Deploy Server

Other Tools