Skip to main content
Glama
Sign In

agdata

by dev.shveik
OverviewDiscussionsAdmin

Search LinkedIn posts

linkedin-post-search
Read-only

Search public LinkedIn posts by keywords or Boolean query, with optional author, age and sort filters. Get post text, dates and engagement as JSON. Use it to find company announcements, product mentions and relevant discussions without knowing the post URLs first. Not offered on Solana: pay on Base or Polygon.

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": {
      "query": "<query>"
    },
    "name": "linkedin-post-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoresult order
limitNonumber of posts wanted, 1 to 20 (default 5). A larger value is lowered to 20 and 0 or a negative one means the default; the quote follows the value used.
queryYeskeywords or Boolean query
postedNomaximum post age
author_urlNooptional LinkedIn profile or company page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, so the description earns credit for adding what they don't: results are public posts returned as JSON with text, dates and engagement, and there is a payment-chain constraint (Base or Polygon, not Solana). It omits rate limits, result caps beyond the schema, and pagination behavior.

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?

Purpose and filters are front-loaded in the first sentence, return shape follows, and use cases come last. The payment-chain sentence is somewhat cryptic in phrasing but does carry real operational information, so it earns most of its place.

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 no output schema, the description correctly fills that gap by naming the returned fields (text, dates, engagement) as JSON, and it covers scope, filters and payment constraints. Only minor gaps remain, such as pagination or result-volume expectations, which the limit parameter largely covers.

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% with self-documenting enums for sort and posted, so the schema carries the parameter burden. The description only restates the filter categories (author, age, sort, keywords/Boolean) without adding syntax or format detail, so the baseline 3 applies.

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 (search public LinkedIn posts) plus the searchable fields and the key distinguishing trait — you don't need post URLs. That last clause separates it from the sibling linkedin-posts, so an agent can route between them without opening a schema.

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 concrete use cases (company announcements, product mentions, relevant discussions) and implicitly contrasts with URL-based post retrieval. It stops short of naming an explicit alternative tool or stating when-not to use it, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agdata toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources