Skip to main content
Glama
Sign In

LivePublicator

by com.livepublicator
OverviewDiscussionsAdmin

Save a draft

create_release

Saves a company's press release as a draft in the signed-in account and checks it: length, structure, links, image size and content. 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. The company, press contact and spokesperson come from the account when you leave them out. Send the image too: image_url, or image_file for a file attached in the chat, with image_is_ai true when it was made with AI. LivePublicator does not change the text. Returns every problem to fix at once, or a private preview link and an edit link. It does not publish and uses no credit. Agencies name the client company and set client_authorized to true.

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.
image_fileNoOptional: an image file the user attached in the chat.
publish_atNoOptional: when to go live, ISO 8601 (e.g. 2026-11-03T14:00:00Z), up to 60 days ahead.
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_nameNoThe 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_websiteNoThe company's website, e.g. acme.com.
client_authorizedNoAgencies: true confirms the client company agreed that you publish this release for it.

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. Changed1 schema field changed
    • addedInput schema / properties / image_file
      Added value: +{
+  "description": "Optional: an image file the user attached in the chat.",
+  "properties": {
+    "download_url": {
+      "type": "string"
+    },
+    "file_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses that LivePublicator will not rewrite the text, that the response is either a full list of problems to fix or a private preview plus edit link, that it consumes no credit and does not publish, and that company/press contact/spokesperson default from the account when omitted. These are exactly the behavioral facts an agent needs and that the annotations cannot express.

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?

It is front-loaded with purpose and validation behavior, and the trigger examples are tightly packed. It runs long as a single paragraph and folds some per-parameter guidance into prose that overlaps the schema, but no sentence is pure 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?

With 19 parameters, no output schema and a non-idempotent write, the description still covers defaults, image handling, agency authorization, validation feedback and the return shape. An agent has enough to call it correctly without opening the schema.

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 coverage is 100%, so the baseline is 3; the description adds real value on top by explaining the account-supplied defaults for company_name/contact fields, the distinction between image_url and image_file (chat attachment), the purpose of image_is_ai, and the agency-only client_authorized flag.

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?

The opening sentence gives a specific verb and resource (saves a press release as a draft) plus the side effect (checks length, structure, links, image). It explicitly excludes publishing, which separates it from publish_release, and the draft/check framing separates it from update_release and preview_press_release.

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?

It gives concrete when-to-use triggers (product launch, feature, partnership, funding, or news just written in a blog post in chat) and instructs the agent to draft the whole release itself. There is no explicit when-not or named sibling routing, but 'It does not publish' implicitly steers to publish_release for that step.

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