Skip to main content
Glama
Foto MCP Server
by thesven

foto_like_post

Likes or bookmarks a Foto post by its post ID, letting users mark photos they want to revisit or engage with.

Instructions

Like or bookmark a post on Foto by post ID.

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_like_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID to like

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden for a write operation and does not meet it. It does not say whether authentication is required, whether the call is idempotent when the post is already liked, what happens with an invalid post ID, or whether anything is returned. The 'like or bookmark' phrasing further leaves the resulting state ambiguous.

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?

It is a single, front-loaded sentence with no filler, which is appropriate for a one-parameter tool. The only cost is the ambiguous 'or bookmark' hedge, which adds words without adding precision.

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?

The tool is simple, but a mutation with no annotations and no output schema needs the description to cover auth, repeat-call behavior, and the relationship to foto_unlike_post, none of which is present. An agent can invoke it, but cannot confidently predict its side effects or error conditions.

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 single postId parameter is already documented as 'The post ID to like'. The description only restates 'by post ID' and adds no format, source, or validation detail beyond the schema, making the baseline 3 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 names a specific verb pair (like or bookmark), the resource (a post), the platform (Foto), and the identifier (post ID), so an agent knows exactly what action it performs. The one weakness is that 'like or bookmark' presents two distinct actions without clarifying whether they are the same underlying state or two separate modes.

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 call this versus the sibling foto_unlike_post, nor any preconditions such as being logged in or the post existing. The only implied context is that you must have a post ID, which the schema already states.

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