Skip to main content
Glama
NewsBlog Composer MCP

NewsBlog Composer MCP

build_publishing_pack

Assembles the final publishing pack—title, labels, slug, description, alt text, and a trademark-safe image prompt—for a blog post ready to save and publish.

Instructions

Final step. Everything needed to publish, in one block.

Returns the title, the Blogger labels line, the custom permalink slug, the search description, the image alt text, and gemini_image_prompt - a paste-ready prompt for Gemini with brand names already stripped, so the banner cannot reproduce a real trademark.

image_style MUST be the style the USER picked. Leave it empty and this tool asks them directly, through the client, and waits for the answer - do not fill it in yourself. The styles it offers are listed in the result under ask_the_user_about_the_image - show the user that list rather than a list written here, which goes stale the moment a style is added. With no style chosen there is no image prompt in the result and save_and_present refuses the pack, because a banner the user was never asked about is the wrong banner.

image_concepts: describe what the banner should show in plain words (the objects and ideas, not the company names), drawn from the article you just wrote. banner_text shortens the headline for the image; banner_kicker adds a smaller second line.

Pass the result to save_and_present as pack and it is written to publish-pack.md alongside the post.

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": {
      "headline": "<headline>"
    },
    "name": "build_publishing_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
entitiesNo
headlineYes
keywordsNo
banner_textNo
descriptionNo
image_styleNo
banner_kickerNo
canonical_urlNo
image_conceptsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.1
    • addedInput schema / properties / banner_kicker
      Added value: +{
      +  "default": "",
      +  "title": "Banner Kicker",
      +  "type": "string"
      +}
    • addedInput schema / properties / banner_text
      Added value: +{
      +  "default": "",
      +  "title": "Banner Text",
      +  "type": "string"
      +}
    • changedInput schema / properties / image_style / default
      Previous value: -"editorial"New value: +""
  2. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose consequential behavior: the tool can block on user input, strips brand names, and refuses to emit a prompt without a style. It stops short of stating whether it writes anything itself or the permissions involved.

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?

Front-loaded with purpose and output list, which is good, but the image_style paragraph runs long and buries the operational instruction inside a discussion of stale style lists. The point survives, but it costs more words than it needs.

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?

There is no output schema, yet the description names every returned field and explains the conditional shape of the result (no style means no image prompt). The gap is the six unexplained input parameters and the absence of any error or permission behavior.

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

Parameters4/5

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

Schema description coverage is 0% across 10 parameters, so the description does real compensating work: it explains image_style (must be the user's pick, empty triggers a prompt), image_concepts (plain objects and ideas, no company names), banner_text, and banner_kicker. The other six parameters (slug, entities, keywords, description, canonical_url, headline) are never explained.

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

Purpose5/5

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

States a specific verb+resource ('build_publishing_pack', 'Final step. Everything needed to publish, in one block') and enumerates the exact artifacts returned. An agent can distinguish this from sibling save_and_present without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names its position in the workflow ('Final step'), the downstream consumer ('Pass the result to save_and_present as pack'), and the failure mode that blocks that handoff ('save_and_present refuses the pack'). Also gives a hard do-not rule for image_style.

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