Skip to main content
Glama

Stop monitoring creators

flypost_unmonitor_creators
Destructive

Stop monitoring LinkedIn creators in this project (ids from flypost_list_monitored_creators). Their gathered posts are deleted too, so they drop out of flypost_search_inspiration. Only creators the user asked to drop.

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": {
      "remove": "<remove>"
    },
    "name": "flypost_unmonitor_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
removeYesMonitored creator ids from flypost_list_monitored_creators.
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the crucial detail of what is actually destroyed: the gathered posts are deleted and the creators vanish from flypost_search_inspiration. When this description was written the agent now knows the blast radius of a monitor removal, not just that it is a mutation.

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?

Short and front-loaded: the action comes first, then the id source, then the side effect, then the guardrail. The parenthetical id reminder is mildly redundant with the schema but earns its place as an inline routing cue.

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 two-parameter destructive tool with full schema coverage and no output schema, the description covers the action, the prerequisite id source, the destructive side effect, and the user-intent guardrail. Nothing an agent needs to call it safely is missing.

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 both 'remove' and 'project_id' are already documented, including the 25-item cap. The description reinforces the id provenance but adds no syntax, format, or batching meaning beyond the schema, so the baseline 3 applies.

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 ('Stop monitoring LinkedIn creators in this project'), and the parenthetical plus the follow-on sentence make clear it is the inverse of the monitor/listing siblings. An agent can distinguish it from flypost_monitor_creators without inspecting either schema.

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?

Gives a clear condition for use ('Only creators the user asked to drop') and names the source of valid ids (flypost_list_monitored_creators), which routes the agent to the right prerequisite call. It does not explicitly name flypost_monitor_creators as the re-add alternative, so it stops short of full when/when-not coverage.

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.