Skip to main content
Glama

Find LinkedIn creators to monitor

flypost_find_creators
Read-only

Find LinkedIn creators who post about given topics, to monitor for inspiration (the Topic Monitoring search). Instant and free, from creators Flypost has already indexed: 1+ keywords, up to 30 results. Try this first; if it finds too few, flypost_deep_search_creators runs a fresh LinkedIn search. Then add the ones the user picks with flypost_monitor_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": {
      "keywords": "<keywords>"
    },
    "name": "flypost_find_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionsNoCountry names, e.g. ["United Kingdom"].
keywordsYes
min_followersNoDefault 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: it is instant and free, it queries only a pre-built index of already-indexed creators, and it caps at roughly 30 results — all of which explain why results may be sparse. It does not describe the shape of returned creator records, which is the remaining gap.

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?

Three tight sentences ordered as purpose, cost/scope, then routing to fallback and follow-up. No restated title or filler; the most decision-relevant fact ("Try this first") is placed before the alternative.

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 3-parameter read tool with no output schema, the definition covers what it does, its cost, its source index, its result ceiling, and both neighboring tools. Only the returned creator fields are left unspecified, a minor gap given the tool's simplicity.

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 coverage is 67% and the description only reinforces the keyword minimum ("1+ keywords") and the result cap. min_followers' default 1000 and regions' country-name format are documented in the schema, not the description, so it adds little meaning beyond structured data. Baseline 3 is appropriate at this coverage level.

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 ("Find LinkedIn creators who post about given topics") plus the motive (monitoring for inspiration) and names the internal search it performs ("the Topic Monitoring search"). An agent can distinguish it from flypost_deep_search_creators and flypost_monitor_creators from the text alone.

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 explicit ordering guidance ("Try this first"), a fallback condition ("if it finds too few, flypost_deep_search_creators runs a fresh LinkedIn search"), and the natural next step ("add the ones the user picks with flypost_monitor_creators"). Both the alternative and the selection condition are stated outright.

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.