Skip to main content
Glama

Save a build in public note

notes_save

Save one note's drafts to Assisted posts in the results app, for the founder to post: x (one post, 280 characters as X counts them, links 23) and or reddit (a subreddit from notes_context, a title, a body). image is the path of the image you made, for the founder to attach. Or, on its own, the long form: article (a flagship X Article: title under 100 characters, a body of 600 characters or more in Markdown with an image line caption where each image goes, the 5:2 cover and the images) or thread (2 to 12 posts of 280 characters, each with its image or none, for an account without X Premium); premium is what you saw on X's Articles tab. The source is marked written, so it is never offered again (an Article on its own, so a source can have a note and an Article); saving again for the same source revises a draft not posted yet. A giveaway's Reddit post can go to up to 4 subreddits, each saved with the same source and its own subreddit. Returns X's composer, the Articles tab, or Reddit's submit page. Nothing is posted. Free.

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": {
      "source": "<source>"
    },
    "name": "notes_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
redditNo
sourceYesThe source from notes_context
threadNoThe same story as an X thread, for an account without X Premium, saved on its own
articleNoA flagship X Article, saved on its own
premiumNoWhether the account has X Premium, from X's Articles tab just now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / article
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "A flagship X Article, saved on its own",
      +  "properties": {
      +    "body": {
      +      "maxLength": 40000,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "cover": {
      +      "maxLength": 500,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "images": {
      +      "items": {
      +        "maxLength": 500,
      +        "type": "string"
      +      },
      +      "maxItems": 8,
      +      "type": "array"
      +    },
      +    "title": {
      +      "maxLength": 200,
      +      "minLength": 1,
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title",
      +    "body",
      +    "cover"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / premium
      Added value: +{
      +  "description": "Whether the account has X Premium, from X's Articles tab just now",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / thread
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The same story as an X thread, for an account without X Premium, saved on its own",
      +  "properties": {
      +    "posts": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "image": {
      +            "maxLength": 500,
      +            "type": "string"
      +          },
      +          "text": {
      +            "maxLength": 2000,
      +            "minLength": 1,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "text"
      +        ],
      +        "type": "object"
      +      },
      +      "maxItems": 12,
      +      "minItems": 2,
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "posts"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Goes well past the annotations: it discloses the side effect that the source is marked written and never offered again (an Article excepted), that repeat saves revise rather than duplicate drafts, that a giveaway's Reddit post can fan out to up to 4 subreddits sharing one source, and that it returns X's composer, Articles tab, or Reddit's submit page. 'Nothing is posted. Free.' clarifies the safety profile the annotations only hint at. Loses a point because these facts are buried in an unstructured run-on, making the key state-change ('marked written') easy to miss.

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

Conciseness3/5

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

Nearly every clause carries information, but it arrives as one long comma-chained sentence with parenthetical nesting ('x (one post, 280 characters as X counts them, links 23) and or reddit'), which reads as dictated rather than structured. The purpose is front-loaded, but the per-variant constraints would be far more scannable as separate lines, and the awkward phrasing ('and or', 'premium is what you saw') risks misparsing.

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?

For a 6-parameter tool with nested objects and no output schema, the description covers the modes, mutual exclusivity, character limits, side effects, and even what the response navigates to. It stops short of describing error behavior or exactly what the returned composer/page representation contains, which matters somewhat given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds substantial meaning beyond a 67%-covered schema: x text is 280 characters as X counts them with links counting as 23, image is a path to an image already made, reddit subreddit comes from notes_context, article title is under 100 characters with a body of 600+ Markdown including ![caption](path) lines and a 5:2 cover, thread is 2–12 posts of 280 characters, and premium is read off X's Articles tab. The schema alone (maxLength 2000 on text) would badly mislead an agent about the real limits, so the description is doing essential work here.

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?

States a concrete verb and resource: it saves one note's drafts into Assisted posts (X, Reddit, Article, or thread) for the founder to post, and it names notes_context as the origin of the reddit subreddit and source. That is far more specific than the bare name, though the sibling most likely to be confused with it (grow_notes_save, notes_voice) is never mentioned, so the agent must infer the boundary from the name alone.

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 real selection conditions: x and/or reddit together, versus article or thread 'on its own', with premium gating article vs thread ('for an account without X Premium'), and states that re-saving the same source revises an unposted draft rather than creating a new one. What is missing is an explicit exclusion — nothing says when not to call this, e.g. after the source is already marked written.

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