Skip to main content
Glama
Sign In
ATProto MCP Server

ATProto MCP Server

by ewanc26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_posts

Find public posts on Bluesky by searching with keywords or phrases. Specify a search query and control the number of results.

Instructions

Search for public posts on Bluesky using keywords or phrases.

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch query string.
limitNoNumber of posts to return (default 25, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so description carries full burden. It only states the basic action, but fails to disclose any behavioral traits like authentication requirements, result ordering, rate limits, or 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?

The description is a single, front-loaded sentence with no fluff. It is concise, though it could be slightly expanded without losing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema or annotations, the description should provide more context about what the tool returns, any required auth, or usage limits. It does not, leaving the agent underinformed for a search tool.

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 describes both parameters. The description's mention of 'keywords or phrases' adds minimal value beyond the schema's 'Search query string.' Baseline 3 applies; no additional semantic enrichment.

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?

The description clearly states the verb 'Search' and the resource 'public posts on Bluesky', with the method 'using keywords or phrases'. It distinguishes from sibling tools like get_author_feed and get_post_thread, which are for specific feeds or threads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use search vs alternatives (e.g., get_author_feed for a specific user's posts). No when-not or contextual hints provided.

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

Deploy Server

Other Tools