Skip to main content
Glama

Stop Monitoring a Profile

untrack_profile
Destructive

Stops monitoring a profile: no further scheduled refresh crawls are charged for it. Free to call. Pass the internal profileId (from list_tracked_profiles or search results). The profile and its already-crawled posts stay in the database and searchable; only the recurring refresh stops. Returns not_found if the profile is not currently being monitored. Cost: free.

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": {
      "profileId": "<profileId>"
    },
    "name": "untrack_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileIdYesInternal profile id to stop monitoring

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses what is and is not destroyed (the profile and already-crawled posts remain searchable, only recurring refresh stops) and the error behavior (not_found), which directly explains why idempotentHint is false. The cost statement is also supplied, which annotations cannot convey.

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 action and its consequence, then the id source, then the persistence caveat and error case. Slight redundancy in stating the cost twice ("Free to call" and "Cost: free") costs a fraction of a point.

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 tool with no output schema, it covers cost, side effects, data retention, and the failure mode, which is nearly everything an agent needs. It does not describe what a successful call returns, which is the one gap given no output schema exists to fill it.

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%, so the parameter is already typed and labeled, but the description adds real meaning by specifying that it must be the *internal* profileId and pointing to the two tools that produce it. That guidance about id provenance is not present in the schema.

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 ("Stops monitoring a profile") and immediately clarifies what that means operationally: no further scheduled refresh crawls are charged. It is cleanly distinguishable from the sibling track_profile by being the inverse operation, and the persistence note separates it from a delete.

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?

The description tells the agent exactly where to obtain the required id (list_tracked_profiles or search results) and names the error condition for calling it on an untracked profile. It stops short of explicitly naming track_profile as the way to re-enable monitoring, but the inverse relationship is obvious from the name.

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