Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_home_feed

Retrieve your chronological Foto home timeline of posts from creators you follow. Set a limit up to 50 to control how many feed posts are returned.

Instructions

Retrieve your chronological Foto home timeline of posts from creators you follow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "foto_get_home_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum feed posts to return (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses chronological ordering and that posts come from followed creators, and "Retrieve" implies a read operation, but it does not state authentication requirements, pagination behavior beyond the schema's limit, or rate limits.

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 definition is a single well-formed sentence with the resource and scope front-loaded. Every phrase adds useful information, with no filler or repetition.

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 read-only feed retrieval tool with one optional, fully documented parameter and no output schema, the description is nearly complete. The main omission is any mention of authentication or pagination semantics, but the core behavior is clear.

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 limit parameter is already documented with its maximum and default. The description adds no additional meaning about how limit affects ordering or pagination, so baseline 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 uses a specific verb, "Retrieve," and identifies the resource as the Foto home timeline of posts from followed creators. It clearly distinguishes the home feed from a general or explore feed through the "creators you follow" scope, though it does not explicitly name a sibling alternative.

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 the feed scope: this is the tool for viewing posts from accounts the user follows. However, it does not explicitly say when to use this instead of foto_get_explore_feed or other discovery tools, so guidance is only implicit.

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