browse_themesBrowse the photo themes available for generation, optionally filtered by gender category or a keyword. Returns the theme slugs that generate_photo expects.
Requires a connected Photo AI Studio account. Calling this tool starts the sign-in flow.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Search themes by name or keyword | |
| gender | No | Filter themes by gender category |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is read-only, idempotent, and non-destructive. The description adds valuable non-obvious behavior: a connected Photo AI Studio account is required and calling the tool starts the sign-in flow. This goes beyond what annotations provide and helps the agent anticipate side effects.
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 short, front-loaded with the tool's main purpose, and immediately followed by the critical output detail and account/sign-in note. Every sentence serves a distinct purpose without redundancy.
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 low parameter count, rich annotations, and simple output (theme slugs), the description covers the essentials: what the tool returns, why it matters, and the auth prerequisite. It stops short of describing the exact response shape or whether tag and gender can be combined, but these are minor given the tool's simplicity.
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?
Schema coverage is 100%, so the schema fully documents tag and gender. The description adds only that filtering is optional and by gender or keyword, which lightly reinforces the semantics but does not materially extend beyond the schema.
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 clearly states a specific action ('Browse'), a resource ('photo themes'), optional filters, and the key output ('theme slugs that generate_photo expects'). However, it does not distinguish browse_themes from its sibling list_photo_themes, which appears to serve a very similar purpose.
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 the tool should be used before generate_photo because it returns the expected slugs, and it mentions the account/sign-in prerequisite. It does not explicitly compare against list_photo_themes or state when not to use this tool, leaving some selection judgment to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.