Skip to main content
Glama

Search Posts

search_posts
Read-onlyIdempotent

[Read · free] Keyword + semantic search over persisted posts in the local library — full-text + pgvector cosine, no LinkedIn pull, free. Use this when the caller has a query string and wants ranked persisted-post results. Pass scope (a post_collections.id) to limit to a specific collection. For fresh LinkedIn keyword pulls, use linkedin_post_search instead (5 credits).

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": {
      "profile_id": "<profile_id>",
      "query": "<query>"
    },
    "name": "search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoSearch mode: hybrid (keyword + semantic), keyword (FTS only), or semantic (embedding similarity only)hybrid
limitNoMax results to return
queryYesSearch query (e.g. 'cybersecurity tips', 'leadership')
scopeNoOptional post_collections.id to restrict results to a collection
profile_idYesTracked profile ID from list_profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description still adds non-obvious behavior beyond that: it runs entirely locally with no LinkedIn pull, costs zero credits vs. 5 for the sibling, and the ranking blends FTS with embedding similarity. It stops short of describing result ordering details or whether scores are returned, which keeps it at 4.

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?

Front-loaded with a compact '[Read · free]' tag, then purpose, then the use/alternative routing. Every clause carries information an agent needs; there is no filler or repetition.

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 a 5-parameter read tool with full schema coverage and annotations, the description supplies everything needed: what it searches, what it costs, what it does not do, and which sibling to use instead. No output schema exists, and the 'ranked persisted-post results' framing is sufficient.

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 `mode`, `limit`, `query`, `scope`, and `profile_id` are all documented in the schema itself. The description only re-surfaces `scope` (post_collections.id) and gestures at the hybrid mode, adding little meaning beyond the structured fields; baseline 3 is appropriate.

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 ('Keyword + semantic search over persisted posts in the local library') plus the mechanism (full-text + pgvector cosine). It explicitly contrasts with the LinkedIn-pull sibling in the same sentence, so an agent can distinguish the two without opening any 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 an explicit use condition ('when the caller has a query string and wants ranked persisted-post results') and names the alternative with its cost differential ('for fresh LinkedIn keyword pulls, use linkedin_post_search instead (5 credits)'). It also tells the agent when to reach for the `scope` parameter.

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.

Resources