Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

bluesky_post

Retrieve a Bluesky post by URL through Fetchproof to access post data for analysis, monitoring, or reference.

Instructions

bluesky: Post. GET /v1/bluesky/post. Get Bluesky post Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "bluesky_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesBluesky post URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the cost model in unusual detail (1 credit on success, free on errors, timeouts, invalid requests, and cache hits, with not-found charged only where the published cost applies), but says nothing about authentication, rate limits, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening 'bluesky: Post. GET /v1/bluesky/post.' restates the tool name and endpoint without adding information the agent can use. The cost paragraph is long, but every clause in it carries real behavioral information, so that part is not filler.

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

Completeness3/5

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

For a single-parameter read tool with no output schema and no annotations, the definition covers billing thoroughly, but it omits what data the post result returns, which is material because an agent cannot tell whether it gets text, media, author, or metrics. The pricing detail compensates somewhat, but the description is not fully complete.

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?

This tool has a single parameter, and the schema description coverage is 100%, so the schema already documents 'url' as 'Bluesky post URL' with a concrete example. The description adds no further semantics, such as accepted URL formats or whether shortened links work, so the baseline score 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?

The description states a specific verb and resource: 'Get Bluesky post', scoped to a single post retrieved via the HTTP endpoint GET /v1/bluesky/post. The URL parameter reinforces that this returns one post rather than a list, which implicitly separates it from bluesky_user_posts, but the description never names that sibling explicitly.

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?

There is no guidance on when to use this tool versus alternatives such as bluesky_user_posts or bluesky_profile, nor any exclusions or prerequisites. The only usage signal is implicit: the required 'url' parameter means you must already have a post URL.

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