Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Draft an X launch post

draft_x_launch_post
Read-onlyIdempotent

Turn a launch into an X (Twitter) post or a numbered thread. Returns posts, each with text, weighted_length (twitter-text parseTweet: 280 max, URLs count as 23, emoji and CJK count extra) and intent_url (https://x.com/intent/post) that opens the composer prefilled. It does not call X, sign in, or post. mode single (default) is one post and refuses over 280; mode thread splits on sentence or word boundaries and numbers posts like 1/3. tone is excited (default), plain, technical, or casual.

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": {
      "project": "<project>",
      "shipped": "<shipped>",
      "url": "<url>"
    },
    "name": "draft_x_launch_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLive URL of the project, http or https. Counted as 23 characters when X recognizes it.
modeNosingle (default) writes one post. thread splits and numbers when the draft is longer than 280.
toneNoVoice of the opening line. Default excited.
projectYesProject name, as it should read in the post
shippedYesWhat shipped, in plain text. This is the body of the post.
hashtagsNoOptional tags, with or without a leading #. One tag per item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe, read-only, idempotent, closed-world operation; the description adds materially beyond them by disclosing the no-network/no-auth/no-post boundary, the exact return shape (text, weighted_length, intent_url), and the 280-character refusal in single mode. It even cites the counting rules used (parseTweet, URLs as 23, emoji and CJK weighted extra), which is the kind of behavioral detail an agent cannot infer.

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 core action and the return shape, then boundaries, then parameter behavior; every sentence carries information. It is a single dense block rather than a structured list, which makes the mode/tone details slightly harder to scan, but there is no 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?

There is no output schema, and the description fully compensates by describing the returned fields and the intent_url behavior. For a six-parameter, non-networking drafting tool, nothing an agent needs to invoke it correctly 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% and every parameter is already documented, including defaults and enum meanings. The description largely restates those (mode single/thread, tone options, URL counted as 23) but adds a little beyond the schema by saying thread splits on sentence or word boundaries and numbers posts as '1/3'.

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 ('Turn a launch into an X (Twitter) post or a numbered thread') and names the output artifacts. It also disambiguates from the obvious false cousin by stating 'It does not call X, sign in, or post', which no sibling tool covers.

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?

Usage is clear from the framing (drafting a launch announcement) and the description explains what selects single vs thread behavior. It stops short of stating when an agent should choose this over an alternative, but no sibling produces social copy, so there is little to route between.

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

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