Skip to main content
Glama
Sign In

ProductClank

by com.productclank
OverviewDiscussionsAdmin

Draft quote posts for one moment

draft_quote_post

Drafts quote posts for ONE moment from the latest find_quote_moments search: the user's caption names the person and topic and adds value on top (value_mode: workflow, breakdown, disagreement, example, implication or opinion — omit to let the drafter pick). Free. url must be a moment url from the latest search. Waits for the drafts (usually under a minute). The drafts also land in the user's Content queue. Show them, help the user edit one; they quote the person's post with it and post from their own account.

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": {
      "space_id": "<space_id>",
      "url": "<url>"
    },
    "name": "draft_quote_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe moment's url (the person's own X post) from the latest search.
space_idYesThe content space (brand) to run it on — from list_content_spaces. No space yet? setup_content_space first.
value_modeNoWhat the caption adds on top of their claim.

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?

Adds considerable context beyond the annotations: the call blocks ('Waits for the drafts, usually under a minute'), it is free, drafts are also written into the Content queue, and the drafts are not published automatically since the user posts from their own account. Latency, cost, side effect and non-publishing behavior are all materially useful and not derivable from readOnlyHint/destructiveHint alone.

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 scope in the first clause, with preconditions, cost and follow-up in a compact order. It is dense and a few parenthetical asides could be trimmed, 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 non-idempotent draft-generation tool with no output schema, the description covers the prerequisite search, required space context, blocking latency, cost, where results land, and the expected follow-up conversation with the user. Nothing an agent needs to call it correctly appears 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, but the description adds real meaning: it enumerates the value_mode choices and explains omission lets the drafter pick, and it reinforces that url is a moment url from the latest search rather than any URL. space_id's brand/space resolution is left to the schema.

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 ('Drafts quote posts') and narrows scope to 'ONE moment' sourced from 'the latest find_quote_moments search', which separates it from generate_posts and write_content_candidates. An agent can identify the operation 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 Guidelines4/5

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

Gives clear preconditions: the moment url must come from the latest find_quote_moments search, and space_id resolution is pointed at list_content_spaces/setup_content_space via the schema. It also says value_mode can be omitted to let the drafter choose. No explicit when-not or named alternative sibling is given, so it stops short of a 5.

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

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