Search Brandize blog posts (logo design and branding guides) by keyword. Returns matching post titles, excerpts, and URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Keyword(s) to match against post titles and content. |
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?
No annotations are provided, so the description carries the full burden. It discloses the core behavior: searching by keyword and returning matching post titles, excerpts, and URLs. The search verb also implies a non-mutating operation, though it does not explicitly address result limits or ordering.
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 sentence that front-loads the action and resource, then specifies the return payload. There is no filler or redundant information.
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?
For a simple one-parameter search tool with no output schema, the description is complete: it states the domain, the search mechanism, and the exact return values. Nothing critical is missing for an agent to invoke it 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?
Schema description coverage is 100%, so the query parameter is already well documented in the schema. The description adds 'by keyword,' which reinforces the parameter's meaning but does not significantly extend beyond the schema's own 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 ('Search') and a clear resource ('Brandize blog posts') with an explicit scope ('logo design and branding guides'). It also states what the tool returns, making it easily distinguishable from the sibling generation and purchase tools.
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 clearly implies when to use the tool: when the user wants to find blog content by keyword. It does not explicitly state when not to use it or name alternatives, but the sibling list contains no other search tool, so the usage context is clear enough.
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 targets a distinct resource or action: logo generation, logo variations, variation purchase, result polling, color palette, meta tags, schema markup, pricing, blog search, and health check. The two logo-generation tools are clearly differentiated by new-job vs existing-job workflows, so an agent should not confuse them.
Most tools follow a clean verb_noun convention: generate_logo, generate_color_palette, get_logo_result, search_blog, buy_logo_variation. The lone echo and the singular/plural mismatch between buy_logo_variation and generate_logo_variations are minor deviations from an otherwise consistent pattern.
With 10 tools, the server is well scoped. The paid logo workflow is covered by generate, vary, buy, and retrieve tools, while supporting tools for palettes, SEO metadata, pricing, and blog search each serve a distinct purpose without bloat.
The core logo lifecycle is well covered: generate, create variations, purchase a variation, and retrieve the paid deliverable. However, the descriptions advertise upgrades and revision credits but provide no explicit tool to purchase or apply them, leaving a minor gap that agents must work around.