Skip to main content
Glama

The Marketing Vault

Write a blog article

write_blog_article

Creates or rewrites blog articles, outlines, full drafts or search and answer-engine enrichment. Output is saved to the Library and uses one generation. Nothing is sent or published.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "template": "<template>",
      "details": "<details>"
    },
    "name": "write_blog_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoMode for the selected template.
briefNoBrief for the selected template.
sourceNoSource for the selected template.
detailsYesWhat the user wants, including supplied source text, goals or constraints.
outlineNoOutline for the selected template.
audienceNoAudience for the selected template.
templateYescreate-or-rewrite: Create or rewrite a blog article. article-outline: Create an article outline. full-draft: Write a full article from an outline. seo-aeo-geo-enrichment: Enrich a draft for search and answer engines.
blog_draftNoBlog draft for the selected template.
word_countNoTarget article word count.
must_includeNoMust include for the selected template.
target_keywordNoTarget keyword for the selected template.
business_profile_idNoBusiness profile id. Required when the account has multiple Businesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnly=false, destructive=false, non-idempotent, closed-world), so the description carries useful extra weight: it discloses that output lands in the Library, that each call consumes one generation, and that nothing is sent or published. Those are exactly the cost and side-effect facts an agent needs before calling. It stops short of noting that repeat calls create additional saved artifacts rather than overwriting.

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?

Two tight sentences, front-loaded with the action and scope, followed by the outcome and cost notes. No filler or restatement of the title.

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 12-parameter, no-output-schema generation tool, the description covers what it produces (a Library entry, not a published post) and what it costs. Minor gaps remain around retrieval of the saved artifact and how the free-form template parameters interact, but nothing blocking.

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% and every parameter, including the four-value template enum, is documented in the schema itself. The description adds no syntax, format, or dependency guidance beyond that, so baseline 3 applies.

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 (creates or rewrites blog articles) and enumerates the four template modes it covers, which maps directly to the enum. It is clearly a blog-writing tool rather than ad, email, or page copy, though it never names those siblings explicitly.

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: the phrase 'creates or rewrites' plus the template list suggests picking this tool when the deliverable is a blog article. There is no explicit 'use this instead of write_page_copy when...' routing and no statement of prerequisites or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources