Skip to main content
Glama

FoxAPIs data sources

Bluesky post

bluesky_post
Read-onlyIdempotent

A Bluesky post: text, author, likes, reposts, replies, quotes and time, from its link. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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
urlYesFor example: "https://bsky.app/profile/bsky.app/post/3n2mkgfb4tk2d"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state read-only, open-world, idempotent, and non-destructive behavior. The description adds useful operational context beyond annotations: 2-credit cost, no charge when no data is returned, and a required FoxAPIs key. It does not cover rate limits or broader error behavior, so a 4 is appropriate.

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?

The description is compact and front-loads the resource and returned fields before the cost and auth notes. Every sentence is informative and there is no unnecessary wording.

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 simple one-parameter read-only retrieval tool with no output schema, the description adequately lists the returned fields and adds billing/auth context. It does not fully specify the shape of returned data such as reply/quote collections, but it is broadly complete for the tool's complexity.

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 single `url` parameter is already well documented with an example. The description adds that the input is the post's link, but it does not add format or validation semantics beyond what the schema 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?

The description identifies the specific resource (a Bluesky post) and enumerates the returned fields, making the tool's retrieval purpose clear. It does not use an explicit verb and does not explicitly differentiate itself from analogous sibling tools, so it falls short of a 5.

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?

The phrase "from its link" implies that the tool should be used when given a Bluesky post URL, and the billing/auth notes clarify prerequisites. However, it gives no explicit when-not-to-use guidance or named alternatives for other platforms.

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