by_userPublic uploads from one user.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| user_id | Yes | Flickr NSID (e.g. "12345678@N00") or screenname. |
| Name | Required | Description | Default |
|---|---|---|---|
| items | No | Array of photo items from the user feed | |
| title | No | Feed title from Flickr |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "limit": 15,
+ "user_id": "12345678@N00"
+ },
+ {
+ "user_id": "flickr_username"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "items": {
+ "description": "Array of photo items from the user feed",
+ "items": {
+ "description": "Photo item object",
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "title": {
+ "description": "Feed title from Flickr",
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds the behavioral constraint that only 'Public' uploads are returned, which is useful. However, it does not disclose details like pagination, sorting, or how the limit parameter affects results beyond what the output schema may already capture.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It conveys the core purpose efficiently, though it is arguably too terse and could benefit from an explicit verb. Still, it is concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and comprehensive safety annotations, the description only needs to state the tool's scope, which it does. However, it omits any mention of parameter behavior, alternatives, or edge cases, making it minimally adequate but not complete for a tool with two parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With schema description coverage at 50%, only user_id is described in the schema and the description adds no parameter context. The limit parameter is undocumented in both the schema and the description, so the agent receives no explanation of its meaning or format. The description does not compensate for the missing limit semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Public uploads from one user' clearly identifies the resource (public uploads) and the scope (one user), distinguishing it from similar tools like by_group. However, it lacks an explicit verb (e.g., 'list', 'retrieve'), so it doesn't fully meet the 5-point criterion for a specific verb+resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as by_group, recent, or search_within. It does not mention exclusions, prerequisites, or contexts where another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.