collection_photosList photos inside a specific Unsplash collection by id; returns paginated photo objects with image URLs and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of items returned. | |
| items | Yes | Array of photos in the collection |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesPrevious value: -[
- {
- "id": "3FusKJf17II"
- },
- {
- "id": "3FusKJf17II",
- "per_page": 25
- }
-]New value: +[
+ {
+ "id": "3FusKJf17II"
+ },
+ {
+ "id": "3FusKJf17II"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, covering the operation's safety profile. The description adds useful behavioral details beyond annotations, such as pagination and the structure of returned photo objects (image URLs and metadata), which helps set expectations.
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 that states the action and the expected output without any verbose or irrelevant content. It is concise and effectively 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?
The tool has one required parameter, a robust annotation set, and an output schema. The description covers the operation, scoping, and output characteristics, making it sufficient for an agent to select and invoke the tool correctly.
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?
The schema has zero description coverage for the sole parameter 'id', but the description clarifies that it is the specific Unsplash collection id, giving the parameter its intended meaning. This fully compensates for the schema's lack of description.
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 uses a specific verb 'List' and clearly identifies the resource as 'photos inside a specific Unsplash collection by id'. This precisely states what the tool does and distinguishes it from sibling tools like list_photos or search_photos.
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 implies usage context by requiring a collection id and describing the operation, making the appropriate use case obvious. However, it does not explicitly mention alternatives or when not to use this tool, which would have made the guidance stronger.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.