Skip to main content
Glama
zhangluka

grain-seo-mcp

by zhangluka

seo_primitive_is_brand

Check if a search query contains brand terms using a customizable regex pattern. Identify brand queries to refine SEO analysis.

Instructions

primitive: Check if a query is a brand query based on a regex pattern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query
brandRegexYesRegex pattern to identify brand terms
engineNoThe search engine (optional)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description bears full burden. It only states the basic function without disclosing read-only nature, potential side effects, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, efficient and to the point. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple check tool, but lacks details about return value (e.g., boolean) and how the optional engine parameter affects behavior. Without output schema, more context on output would help.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters with descriptions (100% coverage). Description adds 'based on a regex pattern' but this is redundant with the schema. Does not add new meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool checks if a query is a brand query using a regex pattern. It distinguishes itself from the sibling 'seo_brand_vs_nonbrand' by being a primitive check, though it doesn't mention the output format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this primitive versus alternative brand analysis tools. Does not specify prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhangluka/grain-seo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server