Skip to main content
Glama

Publish on my share link

share_set
DestructiveIdempotent

Publish content on your share link so a human can see it (HTML, plain text, Markdown, PNG, JPEG or PDF, up to 4 MB): anyone with the link can open it, and each call replaces the last content (same address). Use content for text or content_base64 for images and PDFs. With content_base64 the file can be about 3 MB at most: base64 adds a third and requests are limited to 4.5 MB. The answer has share_url for your human; share_get reads it back.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "# Status\n\nAll tests pass.",
      "instance_id": "shr_exampleexampleexample2",
      "content_type": "text/markdown"
    },
    "name": "share_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoMarkdown: the language of your text as a language tag (en, de, pt-BR), for screen readers. Without it we guess from the text, else en.
titleNoPage title humans see in the browser tab and link previews.
contentNoText content (HTML, plain text, Markdown). Send this or content_base64.
instance_idYesUtility instance id from buy or list_utilities.
content_typeYesWhat you publish; the bytes must match it.
content_base64NoImage or PDF bytes, in standard base64 with = padding.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / content_type / description
      Previous value: -"What you publish."New value: +"What you publish; the bytes must match it."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "content": "# Status\n\nAll tests pass.",
      +    "content_type": "text/markdown",
      +    "instance_id": "shr_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Markdown: the language of your text as a language tag (en, de, pt-BR), for screen readers. Without it we guess from the text, else en.",
      +  "maxLength": 20,
      +  "type": "string"
      +}
  5. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / content / description
      Added value: +"Text content (HTML, plain text, Markdown). Send this or content_base64."
    • addedInput schema / properties / content_base64 / description
      Added value: +"Image or PDF bytes, in standard base64 with = padding."
    • addedInput schema / properties / content_type / description
      Added value: +"What you publish."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / title / description
      Added value: +"Page title humans see in the browser tab and link previews."
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, but the description goes well beyond them: it discloses the public exposure ("anyone with the link can open it"), that each call overwrites the previous content at the same address, the effective payload ceilings (4 MB direct, ~3 MB for base64 because it adds a third, 4.5 MB request limit), and that the response carries share_url. These are exactly the mutation and exposure facts an agent needs before calling.

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?

Information is front-loaded (what it does, who can see it, replacement behavior) before the parameter guidance and limits. It is a dense single block with several colon-separated clauses, slightly run-on, but nearly every clause carries operational value.

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 7-parameter mutation tool with no output schema, the description covers formats, size limits, overwrite semantics, public visibility, and the shape of the response (share_url). Nothing an agent needs in order to call it correctly appears to be missing.

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 earns more by clarifying mutual exclusivity of content vs content_base64 and by explaining the derived size constraint of base64 encoding, which is a real semantic the schema does not state. It does not touch instance_id, content_type matching, or passport_token, but those are already fully documented.

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?

Specific verb+resource ("Publish content on your share link") plus the supported formats and the human-visible outcome. It explicitly names the sibling that reads content back ("share_get reads it back"), so an agent can separate publish from retrieve without opening a schema.

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 clear selection guidance between the two content parameters ("Use content for text or content_base64 for images and PDFs") and the intent trigger ("so a human can see it"). It does not describe when to avoid this tool or what happens if the instance has no active share link, so it stops short of full when/when-not coverage.

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.