Skip to main content
Glama
Sign In

LivePublicator

by com.livepublicator
OverviewDiscussionsAdmin

Preview a release

preview_press_release
Read-onlyIdempotent

Shows how a company's press release will look on LivePublicator, without signing in. Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from the chat: headline, one-sentence summary, body, key facts and questions and answers, plus the quote (name and role), press contact, company name and website, and an image URL if there is one. Returns every problem to fix at once, or a private preview page that expires after 7 days. The preview page has a button to publish it on the LivePublicator website. This tool publishes nothing.

Input Schema

NameRequiredDescriptionDefault
faqNoOptional: up to 6 questions and answers.
bodyYesThe release body, 250 to 1,000 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most.
quoteYesA quote from a real person at the company. More quotes can go in the body.
summaryYesOne sentence that sums up the news (40 to 300 characters).
headlineYesOne line, 10 to 200 characters. Name the company in it.
image_urlNoOptional: a public https URL of a cover image (JPEG, PNG or WebP, up to 5 MB), for example from the company's website or blog post. 1200 px wide or more fills the page; from 600 px it shows at its own size. Under 600 px the release uses the cover card.
key_factsYes1 to 8 short facts, 5 to 200 characters each.
quote_nameYesFull name of the person quoted.
image_is_aiNotrue when the image was made with AI (for example by you, at the user's request). The page then labels it "Illustration, created with AI".
quote_titleYesRole of the person quoted, e.g. Founder and CEO.
company_nameYesThe company the news is about.
contact_nameYesPress contact's name, shown for journalists.
contact_emailYesPress contact's email.
contact_phoneNoOptional press contact phone.
contact_titleYesPress contact's role.
company_websiteYesThe company's website, e.g. acme.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / body / description
      Previous value: -"The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most."New value: +"The release body, 250 to 1,000 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most."
  2. Changed1 schema field changed
    • changedInput schema / properties / image_url / description
      Previous value: -"Optional: a public https URL of a landscape cover image, at least 1200 px wide (JPEG, PNG or WebP, up to 5 MB), for example from the company's website or blog post."New value: +"Optional: a public https URL of a cover image (JPEG, PNG or WebP, up to 5 MB), for example from the company's website or blog post. 1200 px wide or more fills the page; from 600 px it shows at its own size. Under 600 px the release uses the cover card."
  3. Changed2 schema fields changed
    • addedInput schema / properties / image_is_ai
      Added value: +{
+  "description": "true when the image was made with AI (for example by you, at the user's request). The page then labels it \"Illustration, created with AI\".",
+  "type": "boolean"
+}
    • changedInput schema / properties / image_url / description
      Previous value: -"Optional: a public https URL of a landscape cover image, at least 1200 px wide (JPEG, PNG or WebP, up to 5 MB)."New value: +"Optional: a public https URL of a landscape cover image, at least 1200 px wide (JPEG, PNG or WebP, up to 5 MB), for example from the company's website or blog post."
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial detail beyond them: all validation problems are returned at once, the preview page is private and expires after 7 days, and it contains a publish button. That is exactly the context an agent needs to set user expectations.

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?

Front-loaded with the purpose and the 'publishes nothing' caveat, and every sentence carries information. The drafting instruction is a long dense run-on that could be split, but no sentence is filler.

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

Completeness5/5

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

For a 16-parameter, 12-required tool with no output schema, the description covers what to supply, what comes back (validation errors or a preview URL with a 7-day expiry), and the safety profile. Nothing needed to call it correctly is missing.

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%, so fields, formats and limits are already documented. The description enumerates the fields to draft (headline, summary, body, key facts, Q&A, quote, contact, website, image URL), which is helpful framing but adds little syntax or constraint detail beyond the 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?

States a specific verb and resource ('Shows how a company's press release will look on LivePublicator') and explicitly separates itself from publishing ('This tool publishes nothing'). It doesn't explicitly contrast with create_release or fix_live_release, so sibling differentiation is only partial.

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

Usage Guidelines4/5

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

Gives concrete triggers ('use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding') and covers the blog-post case. It implies but never states when to prefer create_release or publish_release instead.

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

All LivePublicator 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