search_programsSearch affiliate programs by keyword, category, or commission type
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search keyword to match against name, description, tags, or category | |
| category | No | Filter by category name (e.g. 'AI & ML Tools', 'Email Marketing') | |
| verified_only | No | When true, return only verified programs | |
| commission_type | No | Filter by commission type |
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?
The annotation readOnlyHint=true already communicates the read-only safety. The description adds no further behavioral context such as result format, pagination, or filtering nuances beyond what the schema provides. It neither contradicts nor enriches the annotation.
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 concise sentence, front-loaded with the primary action and resource, followed by the search dimensions. No unnecessary words or repetition.
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 simple purpose, the annotations cover safety, and the schema documents all parameters, the description adequately summarizes the tool's function. It could be slightly more explicit about the return type (e.g., 'returns matching programs'), but overall the context is sufficient.
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?
All four parameters have full descriptions in the schema, so the description doesn't need to add parameter details. It does mention keyword, category, and commission type, which aligns with the schema, but doesn't provide extra meaning beyond the schema's own documentation.
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 the verb 'Search' and the resource 'affiliate programs', and specifies the search dimensions (keyword, category, commission type). This distinguishes it from sibling tools like get_program (single retrieval) and list_categories (category listing).
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 for finding programs by various filters but does not explicitly state when to prefer this tool over alternatives or mention any exclusions. There is no guidance on when to use get_program or list_categories instead.
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.
Each tool has a clearly distinct purpose: retrieving a specific program's details, listing categories, and searching programs. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: get_program, list_categories, search_programs. The naming is predictable and uniform.
Three tools is well-scoped for a focused affiliate program directory. Each tool serves a necessary function without redundancy or bloat.
The core workflows of discovering and retrieving affiliate program details are covered. A minor gap is the lack of a direct 'list all programs' tool, but search_programs can fulfill this need, so it's a workable limitation.