Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_post

Retrieve a Foto post's full details by post ID, including high-resolution image URL, camera EXIF metadata, and engagement stats.

Instructions

Retrieve complete details for a single Foto post by post ID, including high-res image URL, technical camera EXIF, and engagement stats.

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": {
      "postId": "<postId>"
    },
    "name": "foto_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.5/5.0
Behavior2/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. "Retrieve" implies a read, but it never states auth requirements, what happens for a nonexistent or private post ID, or whether the call is rate limited; the enumeration of returned fields is the only real behavioral disclosure, and it exists mainly because there is no output schema.

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?

One front-loaded sentence with zero filler; the action, the resource, and the returned content are all packed in without redundant phrasing.

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 one-parameter read tool, the description covers the essential contract and compensates for the absent output schema by naming the notable fields returned. The remaining gap is failure and permission behavior, which matters but is minor relative to the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter with complete schema coverage, so the schema already explains postId fully. The description only reinforces that lookup is by post ID and adds nothing about format or source of the ID, which is acceptable at this parameter count.

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 ("Retrieve complete details for a single Foto post") and enumerates the payload (image URL, camera EXIF, engagement stats), so an agent knows exactly what it gets back. It does not explicitly distinguish itself from neighbors like foto_get_post_likes or foto_get_comments, relying on the "complete details" framing to imply the difference.

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 implied by "by post ID" — call it when you have a post ID and need the full record. There is no explicit when-to-use versus when-not guidance, no mention of the feed or likes siblings as alternatives, and no stated prerequisites such as auth.

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