Skip to main content
Glama

Start monitoring creators

flypost_monitor_creators

Start monitoring LinkedIn creators (from flypost_find_creators, or LinkedIn profile URLs the user gives you) on the given topics, which also starts gathering their recent posts. The plan caps monitored creators (Creator 3, Pro and Agency 25), and a person can be monitored in only one of the user's projects; anything refused is listed under skipped. Add only creators the user chose. To stop monitoring some, use flypost_unmonitor_creators.

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": {
      "add": "<add>",
      "topics": "<topics>"
    },
    "name": "flypost_monitor_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
addYes
topicsYesWhat their posts are matched against.
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it as a non-read-only, open-world, non-destructive write; the description goes well beyond that. It discloses plan-based caps (Creator 3, Pro/Agency 25), the constraint that a person can only be monitored in one of the user's projects, and that refused entries surface under 'skipped' — exactly the side-effect information an agent needs before mutating state.

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?

Four front-loaded sentences with no filler; prerequisites, caps, and the routing hint each carry weight. The parenthetical source list and the trailing 'skipped' clause make it dense, but nothing is redundant enough to cut.

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?

There is no output schema, and the description compensates partially by noting that rejected creators appear under 'skipped', while caps and the cross-project uniqueness rule cover the main failure modes. It stops short of describing what a successful response contains (e.g., the newly monitored creator records), which is the only remaining gap for a write tool.

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 67% and the description adds real meaning: it clarifies that 'add' entries can originate from a search (hence optional creator_id) or from raw profile URLs, and it explains the one-project-per-person constraint that governs the call. It leaves project_id entirely to the schema's own 'omit for the active project' note.

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 ('Start monitoring LinkedIn creators... on the given topics') and adds the side effect of gathering recent posts. It also names the sibling it is not (flypost_unmonitor_creators) and the sibling that feeds it (flypost_find_creators), so an agent can distinguish it without opening schemas.

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?

Gives the two legitimate input sources (flypost_find_creators results or user-supplied profile URLs), an explicit caution ('Add only creators the user chose'), and routes the opposite operation to flypost_unmonitor_creators. When-to-use and when-to-use-something-else are both 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.