PostToData

Search posts

search_posts

Read-only

Find public posts that match a query. Returns compact, cited results (each item has a url). Works on: bluesky, hackernews, youtube, reddit, x, tiktok, instagram, threads, xiaohongshu, douyin. Requires a prepaid API key.

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

Input Schema

Name	Required	Description
`sort`	No	Result order. top = most popular: use it when the person asks for hot, popular, most-liked or top discussions. latest = newest first. Left out, the platform orders by relevance.
`limit`	No	Items to return, 1 to 50. Default 10.
`query`	Yes	Search text.
`cursor`	No	Opaque cursor from page.next_cursor of the previous response.
`platform`	Yes	Which platform to read. Live now: Bluesky, Hacker News, YouTube, Reddit, X (Twitter), TikTok, Instagram, Threads, Xiaohongshu (RedNote), Douyin.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's added value is what it discloses beyond them: results are compact and cited with a url per item, the supported platform set is enumerated, and an auth requirement is stated up front. It does not mention rate limits, quota consumption, or empty-result behavior, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the core action, then return shape, then the platform inventory, then the auth requirement. Nothing is redundant and the most decision-relevant facts come first.

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?

For a five-parameter search tool with no output schema, the description covers purpose, result shape (compact cited items with urls), platform coverage, and the prepaid-key prerequisite. Pagination is left to the cursor parameter's schema description, which is a minor gap rather than an omission.

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 description coverage is 100%, with sort and platform enums fully documented in-schema, so the baseline is 3. The description restates the platform list (with display names) but adds no syntax, format, or interaction guidance for query, limit, or cursor beyond what the schema already provides.

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 ("Find public posts that match a query") and narrows scope to public content, which separates it from single-post or per-user siblings by implication. It never names an alternative tool explicitly, so an agent must infer the boundary from the word "query" rather than being told.

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

Usage Guidelines3/5

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

Usage is only implied: the query-plus-platform shape signals keyword search, and the closing sentence gives a real prerequisite ("Requires a prepaid API key"). There is no statement of when to prefer this over get_user_posts or get_trending, and no exclusions or failure conditions beyond the auth note.

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

All PostToData tools Inspect

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

Need Help?