Skip to main content
Glama

Share post by public link

share_post
Idempotent

Get a public link to one post, with its replies, for the user to send to someone outside the workspace. Whoever has the link reads the post as it is when they open it, with no sign-in, until it is unshared or the post is deleted; a draft, a scheduled post and a published one can all be shared. A post already shared answers with the link it has. Only for when the user asks for a link to share or show a post: no other tool returns the link, and none should be made unasked.

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": {
      "post_id": "<post_id>"
    },
    "name": "share_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesthe post id

Output Schema

NameRequiredDescriptionDefault
linkYes
noteYes
createdYes
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the link is readable with no sign-in, that readers see the post in its current state at open time rather than a snapshot, that access ends on unshare or deletion, that drafts and scheduled posts are shareable too, and that re-sharing returns the existing link (consistent with idempotentHint=true and readOnlyHint=false). This is the kind of access-control and state-change context an agent needs before creating a public surface.

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 action and result, then the behavioral caveats, then the routing rule. Every sentence carries information, though the closing clause ('no other tool returns the link, and none should be made unasked') is slightly compressed and could be phrased more plainly.

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?

An output schema exists, so return-value description is unnecessary, and the remaining complexity — public access, no sign-in, live content, lifecycle end, idempotent re-share — is all covered. Nothing an agent needs in order to call this correctly or safely 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 coverage is 100% for the single post_id parameter, so the baseline is 3. The description adds only indirect meaning — that post_id can refer to a draft, scheduled, or published post, and that an already-shared post yields its existing link — without describing format or accepted id forms.

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 and resource ('Get a public link to one post, with its replies') plus the audience ('someone outside the workspace'), which separates it cleanly from get_post (private read) and unshare_post (removal of the link). The agent knows exactly what this returns without opening the 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?

Explicit trigger is given ('Only for when the user asks for a link to share or show a post') along with a negative constraint ('none should be made unasked') and the reason ('no other tool returns the link'). The unshared/revoked lifecycle is also referenced, implicitly pointing at unshare_post as the counterpart.

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