Skip to main content
Glama

List monitored creators

flypost_list_monitored_creators
Read-only

The LinkedIn creators this project monitors, with their topics and when their posts were last gathered.

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": "flypost_list_monitored_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing what comes back — per-creator topics and last-gathered timestamps — which matters because there is no output schema. It does not mention ordering, pagination, or the empty-list case.

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?

One compact sentence with no filler, and the most important information (which creators, what data) is front-loaded. It reads as an appositive fragment rather than a complete statement, which slightly weakens clarity but wastes nothing.

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 one-optional-parameter, read-only list tool with no output schema, stating the fields returned is the key missing piece and it is present. Annotation coverage handles safety, so the only real omission is guidance on when to pick this over the search/find siblings.

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?

The single parameter project_id has 100% schema description coverage including the 'omit for the active project' default, so the schema carries the semantics. The description adds nothing about project targeting; baseline 3 applies when coverage is high.

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?

The description names the specific resource ('LinkedIn creators this project monitors') and its scope, which distinguishes it from find/deep-search siblings by the 'monitored' qualifier. It is a noun phrase rather than a verb-led sentence, but the operation (list what's being monitored) is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of related tools such as flypost_monitor_creators or flypost_unmonitor_creators. The agent must infer that this is the read-side counterpart to the monitor/unmonitor pair from the name alone.

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.