Skip to main content
Glama
Sign In

WhizzyCommerce

by com.whizzycommerce
OverviewDiscussionsAdmin

seo_set

Set how the shop describes itself to search engines. Money is integer minor units (cents). Calling this changes nothing: it returns a preview of what would change and a confirmation link. Only the merchant, on that page, can make it happen.

Input Schema

NameRequiredDescriptionDefault
seoTitleNoThe title search results show for the shop, cut at about 60 characters. Empty falls back to the shop's name.
robotsTxtNoThe shop's robots.txt as crawlers read it. Empty, or the same as the platform's own, goes back to the platform's rules.
robotsPolicyNoWhat every page tells crawlers. index_follow is the normal choice; noindex takes the shop out of search results.
robotsSitemapsNoWhich sitemaps robots.txt names, as paths like /sitemap.xml or /pt/sitemap.xml. null names all of them, including languages published later.
seoDescriptionNoThe line under the title in search results, cut at about 155 characters. Empty falls back to the tagline.
socialImageUrlNoThe picture shown when the shop's address is shared on social networks, as a full https:// URL. Empty clears it.
structuredDataNoWhat search engines are told about the business beyond its other settings, on every page: Settings > Search engines > Business in search results. Only the fields given change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / structuredData / properties / verifications
      Added value: +{
+  "description": "Site ownership tags to put in the head of every page, pasted as the service gives them, one <meta> per line: Trustpilot's trustpilot-one-time-domain-verification-id, Google's google-site-verification, Bing's msvalidate.01, Pinterest's p:domain_verify, Meta's facebook-domain-verification. Replaces the list; only verification tags are kept. Settings, Search engines, Verification tags.",
+  "maxLength": 4000,
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

This is the description's strongest contribution. Against annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), it discloses the critical non-obvious behavior: calling it changes nothing, it returns a preview plus a confirmation link, and only the merchant can apply the change. That prevents an agent from falsely reporting the settings as updated and explains why readOnlyHint is false despite no immediate mutation.

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

Conciseness4/5

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

Three short sentences, front-loaded with purpose, then the preview/confirm constraint. The money-units sentence sits oddly between purpose and the critical no-op disclosure, slightly interrupting the flow. Otherwise every sentence earns its place.

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

Completeness4/5

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

For a 7-parameter tool with nested objects, no required fields, and no output schema, the description supplies the one thing an agent cannot infer: that the call is a staged preview requiring merchant confirmation. It leaves unstated whether partial updates merge (the schema's 'Only the fields given change' covers it) and what the preview payload looks like, which is acceptable given the annotation profile.

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 description coverage is 100% with rich per-field docs (robotsPolicy enum, structuredData.hours seven-entry rule, verifications format), so the schema carries parameter meaning. The description only adds the money-is-integer-minor-units note, which is relevant to structuredData.returns.fee but phrased as 'cents' while the schema says minor units of the shop's currency — marginally helpful, slightly imprecise.

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?

States a specific verb and resource: setting how the shop presents itself to search engines (title, robots, structured data). It is clearly distinct from the settings_* siblings and shopping_feeds_set, though it never names a sibling to route against. The purpose is unambiguous without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this when the merchant wants to change SEO/business-listing metadata. There is no explicit when-to-use vs. when-not, and no pointer to alternatives such as settings_identity or settings_details for overlapping shop-description data. The confirmation-flow explanation is behavioral, not routing guidance.

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

All WhizzyCommerce toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources