Skip to main content
Glama
Sign In

WhizzyCommerce

by com.whizzycommerce
OverviewDiscussionsAdmin

blog_posts_create

Write a blog post. 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
bodyYesThe post as HTML: <p>, <h2>, <h3>, <ul>, <a>. Markdown is not read.
tagsNoMade when missing.
titleYes
authorNoAn existing author by name or address.
handleNoThe web address under the blog. Made from the title when omitted.
statusNoDefault draft.
excerptNoA short plain-text summary shown in lists. Made from the body when omitted.
coverAltNoWhat the cover shows, for screen readers and search engines.
coverUrlNoThe cover picture: a public http(s) address of an image. It is fetched and copied onto the shop's storage.
featuredNo
publishAtNoISO date and time with its offset, for published: a future one schedules the post, e.g. one a week for a month of posts.
categoriesNoExisting categories by name or address; unknown ones are skipped.
seoDescriptionNoWhat search engines show, under 160 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"A new post on the shop's blog. A draft unless status is published."New value: +"A new post on the shop's blog. A draft unless status is published; published with a future publishAt schedules it."
    • addedInput schema / properties / publishAt
      Added value: +{
+  "description": "ISO date and time with its offset, for published: a future one schedules the post, e.g. one a week for a month of posts.",
+  "type": "string"
+}
  2. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The annotations declare readOnlyHint=false, implying the tool is not read-only, while the description explicitly says 'Calling this changes nothing' and that only the merchant can make the change happen. This directly contradicts the annotation's read-only signal, so despite useful disclosure of the preview/confirmation workflow, the contradiction requires a score of 1.

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

Conciseness3/5

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

The purpose is front-loaded and the confirmation workflow is stated clearly, but the second sentence about money in integer minor units is irrelevant to a blog post creation tool and does not earn its place. The definition is short but contains a distracting, non-applicable detail.

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 13-parameter creation tool with 85% schema coverage and no output schema, the description supplies the essential behavioral context: it previews changes and requires merchant confirmation. The schema covers parameter details, and the annotations cover safety traits, though the contradictory read-only signal and irrelevant money note keep it from being fully complete.

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

Parameters2/5

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

Schema description coverage is high at 85%, so the schema already documents parameters thoroughly. The description's only parameter-like statement is 'Money is integer minor units (cents),' but the schema contains no money parameter at all, making this misleading rather than additive.

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?

The description clearly states a specific verb and resource: 'Write a blog post.' It distinguishes itself as a creation tool by name, but it does not explicitly contrast with siblings such as blog_posts_edit or blog_posts_set_status. The unrelated money sentence slightly muddies the purpose but does not obscure the core action.

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?

The description explains the important two-step confirmation flow: the call returns a preview and confirmation link, and only the merchant can complete the action. However, it does not state when to use this tool versus alternatives like blog_posts_edit or blog_posts_set_status, nor does it provide exclusions or prerequisites.

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