Skip to main content
Glama

Search posts from monitored thought leaders

flypost_search_inspiration
Read-only

Search the posts gathered from the LinkedIn thought leaders this project monitors (the Inspiration / Monitoring feature). With no query it returns their biggest outperformers: posts ranked by reactions against that creator's own median (vs_creator_median = 3 means 3x their usual). With a query it keyword-matches post text and topics. Sort by 'recent' to catch LinkedIn news and changes creators are talking about this week. Use it to learn what is resonating and what is being discussed — never to copy another creator's wording or pass off their claims as the user's. Read-only and unbilled.

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_search_inspiration"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts to return (default 15).
queryNoKeywords to match, e.g. "algorithm change", "hooks", "profile". Omit to browse top performers.
creatorNoOnly posts by creators whose name contains this.
sort_byNoDefault: relevance with a query, outperformance without.
project_idNoProject id; omit for the active project.
since_daysNoWindow in days (default 90). Use 7-14 for news.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive; the description adds 'unbilled' and, more importantly, explains the ranking model behind results (vs_creator_median = 3 means 3x that creator's usual). It also discloses an ethical constraint about not copying wording or passing off claims. Return shape and pagination behavior are still unstated.

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 what is searched and what the two modes return, then concrete sorting advice. Every sentence carries content, though the closing ethics sentence, while useful, slightly dilutes the operational focus.

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?

With six all-optional parameters, full schema coverage, and no output schema, the description covers intent, the with/without-query split, ranking interpretation, and defaults sufficiently for correct invocation. Only the nature of returned fields is left implicit, which is acceptable given there is no output schema to lean on.

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 100%, so the schema already documents every parameter including defaults and the 'use 7-14 for news' hint. The description adds interpretive meaning for the outperformance metric tied to sort_by, but largely restates the no-query behavior the schema already covers, so the baseline of 3 is appropriate.

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?

States a specific verb and resource plus a precise scope: posts gathered from LinkedIn thought leaders this project monitors (the Inspiration/Monitoring feature). That scope implicitly separates it from creator-discovery tools like flypost_deep_search_creators, but no sibling tool is named explicitly, so differentiation relies on the agent's inference.

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 clear when-to-use conditions: omit the query to see outperforming posts, pass a query to keyword-match text/topics, sort by 'recent' to catch this week's LinkedIn news, and use it to learn what resonates. It does not state when to prefer an alternative tool (e.g. brain or source-doc search), which keeps it short of a 5.

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.