Skip to main content
Glama

Deep-search LinkedIn for creators to monitor

flypost_deep_search_creators
Read-only

A fresh LinkedIn search for creators who post about given topics, for paid plans: needs 5+ keywords (topics, phrases, job titles), up to 20 results, and takes several minutes. It waits about 90 seconds and returns what it has; while status is 'running', collect the rest with flypost_get_creator_search and the returned job_id. Use flypost_find_creators first. 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_deep_search_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoHow closely results must match; default 'balanced'.
regionsNoCountry names, e.g. ["United Kingdom"].
keywordsYes
min_followersNoDefault 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds behavior an agent cannot infer from those: it takes several minutes, it returns partial results after ~90 seconds, the partial result carries a job_id and a 'running' status, and access is gated to paid plans. That fully explains the async contract and its failure/partial mode.

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-loaded with the operation and its constraints, then the workflow ordering, which is the right priority. It is dense but every sentence carries information; the 'takes several minutes' / 'waits about 90 seconds' pairing is slightly redundant but clarifies total versus blocking duration.

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 an async, plan-gated search with 4 params and no output schema, the definition covers plan eligibility, input requirements, latency, partial-result semantics, the job_id handoff, and the surrounding workflow. There is no output schema, yet the description explains what comes back well enough to act on.

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 75% (depth, regions, min_followers are documented), and the description adds real meaning for keywords — topics, phrases, or job titles — beyond minItems/maxItems. The phrase 'up to 20 results' is slightly ambiguous since maxItems=20 applies to keywords in the schema, which could mislead about result count.

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 — 'A fresh LinkedIn search for creators who post about given topics' — and immediately scopes it ('for paid plans'), which separates it from the cached/lightweight sibling flypost_find_creators named later in the text. An agent can identify this tool's job without opening the schema.

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 prerequisites and ordering: 'Use flypost_find_creators first. Then add the ones the user picks with flypost_monitor_creators.' It also names the continuation tool (flypost_get_creator_search) and the exact condition that triggers it ('while status is running'). When-to-use, what-to-do-before, and what-to-do-after are all present.

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.