Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

learn_creator_style

Analyze a specific creator's tweets and generate a writing style rulebook that captures how they write. The rulebook is saved to the creator's profile and can later be used to write posts in that creator's style.

    IMPORTANT: Before calling this tool, ask the user for the X/Twitter username of the creator they want to learn from.

    This tool will:
    1. Fetch the creator's profile and tweets
    2. Analyze their writing patterns, tone, structure, and quirks
    3. Generate a comprehensive style rulebook
    4. Save it to the creator's profile

    Note: The creator must have viral tweets stored in the system. If they don't, the tool will return an error.

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": {
      "username": "<username>"
    },
    "name": "learn_creator_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesThe X/Twitter username of the creator to analyze (without @). Example: 'naval', 'paulg', 'sama'

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true; the description goes beyond them by explaining exactly what gets written (a rulebook saved to the creator's profile), what external data is fetched (profile and tweets), and the failure mode when no viral tweets exist. It does not state whether re-running overwrites an existing rulebook, which matters given idempotentHint=false.

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?

The core action is front-loaded in the first sentence, and the critical precondition is bolded and placed before the details. The numbered list partly restates the opening sentence (generate rulebook, save to profile), costing some efficiency but aiding scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so partially: it states the side effect (rulebook saved to profile) and the error case, but not whether the generated rulebook is returned in the response. For a one-parameter tool with declared annotations, this is nearly complete.

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?

There is a single parameter with 100% schema description coverage, including format guidance ('without @') and examples, so the baseline is 3. The description adds only the instruction to obtain the username from the user and the implicit constraint that it must belong to a creator with stored viral tweets.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Analyze a specific creator's tweets and generate a writing style rulebook.' It also implies the downstream relationship to style-based writing (write_like_creator), though it never names that sibling explicitly, so differentiation relies on inference.

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?

Strong guidance is given: the 'IMPORTANT' block tells the agent to ask the user for the X/Twitter username before calling, and the note states the prerequisite that the creator must have viral tweets stored or the tool errors. There is no explicit statement of when to prefer this over alternatives such as write_in_my_style, which keeps it below a 5.

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

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