Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Bluesky post

bluesky_post_get
Read-onlyIdempotent

Fetch a single Bluesky post by URL to access its content and metadata for verification, research, or citation.

Instructions

Get a single Bluesky post by URL. Requires url.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "bluesky_post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Bluesky post.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds no behavioral context beyond that - nothing about failure modes for invalid or non-Bluesky URLs, whether deleted or private posts error out, or what the returned payload contains.

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?

Two short sentences, front-loaded with the action and resource. Nothing is wasted, though the second sentence largely restates what the schema's required list already shows, making it low-value rather than harmful padding.

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?

There is no output schema, so the description should describe what a post record contains or how failures surface, and it does neither. For a tool with three required parameters including an analytics field and a conversation-id echo protocol, the description leaves an agent without any behavioral picture.

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%, so the schema already documents url, context, llm_model, and conversation_id in detail. The description only echoes the url requirement and says nothing about the other three required parameters, but per the high-coverage baseline a 3 is appropriate since the schema carries the semantics.

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?

"Get a single Bluesky post by URL" gives a specific verb (get), resource (post), and cardinality (single), which separates it from the *_posts_list and *_comments_list siblings. It stops short of naming any sibling explicitly, so differentiation relies on the reader inferring from 'single'.

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?

The only usage statement is "Requires `url`," which is a parameter precondition already stated in the schema, not a when-to-use rule. There is no guidance on when to pick this tool over bluesky_profile_posts_list or the platform-equivalent post_get tools.

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