Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_ai_action_for_shared_link

Apply an AI Action to messages behind share link IDs. Provide a prompt ID and share link IDs to get AI-generated responses for those shared messages.

Instructions

Run an AI Action (Prompt) against one or more shared messages, addressed by share link ID. USE WHEN: You have share link IDs — from create_message_share_link, or a link someone gave you — and want an AI Action applied to the messages behind them. USE INSTEAD: run_ai_action if you have the message IDs directly; going through a share link adds nothing when you already have access. FIRST: share_link_ids comes from create_message_share_link (field id) — call it first if you don't have one. FIRST: prompt_id comes from list_ai_actions (field id) — call it first if you don't have one. EXAMPLE: {"prompt_id":"prompt-abc","share_link_ids":["share-abc"]} RETURNS: {share_link_ids, responses: [{language, text?, markdown?, html?, json?}], ...}. ERROR NOT_FOUND: A share link ID does not exist, or its access has been revoked or expired. — Create a fresh link with create_message_share_link, or verify the ID with get_message_share_link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoResponse language. Defaults to the original message language.
prompt_idYesAI Action ID, from `list_ai_actions` (its `id`).
share_link_idsYesShare link IDs, from `create_message_share_link` (its `id`).
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.10.0
    • addedInput schema / properties / language / description
      Added value: +"Response language. Defaults to the original message language."
    • addedInput schema / properties / prompt_id / description
      Added value: +"AI Action ID, from `list_ai_actions` (its `id`)."
    • addedInput schema / properties / response_fields
      Added value: +{
+  "description": "Dot-path allowlist to shrink the response, e.g. [\"results.id\",\"total\"]. Omit for the full payload.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / share_link_ids / description
      Added value: +"Share link IDs, from `create_message_share_link` (its `id`)."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description does not contradict these. It adds substantial behavioral context beyond the annotations: the exact NOT_FOUND error semantics (nonexistent, revoked, or expired links), remediation steps (create a fresh link or verify with get_message_share_link), and the response envelope shape. This is precisely the kind of failure-mode and recovery disclosure an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average but highly structured with scannable prefixes (USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS, ERROR). Every sentence earns its place: purpose, routing, prerequisites, an example, return shape, and error handling. There is no filler or repetition of schema content.

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 4-parameter tool with no output schema, the description is complete: it covers what the tool does, when to use it vs. the sibling, prerequisites and their source calls, a worked example, the return format, and error conditions with remediation. An agent has everything it needs to select and invoke this tool correctly.

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 value beyond the schema by specifying provenance for the two required parameters: `share_link_ids` comes from `create_message_share_link` (field `id`) and `prompt_id` from `list_ai_actions` (field `id`), plus a concrete example JSON. It doesn't add param-level detail for `language` or `response_fields`, but the schema already covers those adequately.

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 first sentence states a specific verb+resource: 'Run an AI Action (Prompt) against one or more shared messages, addressed by share link ID.' This precisely identifies what the tool does and immediately differentiates it from the sibling `run_ai_action` by establishing the share-link addressing mechanism.

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?

The description provides explicit routing: 'USE WHEN' states the trigger condition (having share link IDs), and 'USE INSTEAD: run_ai_action if you have the message IDs directly' names the alternative and the decision rule. The 'FIRST' instructions also clarify prerequisite calls. Nothing is left to inference.

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

Deploy Server

Other Tools