Skip to main content
Glama

telegraph_create_account

Create a Telegraph account to manage articles programmatically. Save the returned access token for future API requests.

Instructions

Create a new Telegraph account. Returns an Account object with access_token that should be saved for future requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_nameYesAccount name (1-32 characters)
author_nameNoDefault author name used when creating new articles (0-128 characters)
author_urlNoProfile link opened when users click on the author name (0-512 characters)

Implementation Reference

  • Handler for the 'telegraph_create_account' tool: parses input with CreateAccountSchema, calls telegraph.createAccount, and returns the result as JSON text content.
    case 'telegraph_create_account': {
      const input = CreateAccountSchema.parse(args);
      const result = await telegraph.createAccount(
        input.short_name,
        input.author_name,
        input.author_url
      );
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(result, null, 2),
        }],
      };
    }
  • Zod input schema for validating parameters of the 'telegraph_create_account' tool.
    export const CreateAccountSchema = z.object({
      short_name: z.string().min(1).max(32).describe('Account name (1-32 characters)'),
      author_name: z.string().max(128).optional().describe('Default author name (0-128 characters)'),
      author_url: z.string().max(512).optional().describe('Default profile link (0-512 characters)'),
    });
  • Tool registration definition for 'telegraph_create_account' within the accountTools export array, specifying name, description, and JSON input schema.
    {
      name: 'telegraph_create_account',
      description: 'Create a new Telegraph account. Returns an Account object with access_token that should be saved for future requests.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          short_name: {
            type: 'string',
            description: 'Account name (1-32 characters)',
            minLength: 1,
            maxLength: 32,
          },
          author_name: {
            type: 'string',
            description: 'Default author name used when creating new articles (0-128 characters)',
            maxLength: 128,
          },
          author_url: {
            type: 'string',
            description: 'Profile link opened when users click on the author name (0-512 characters)',
            maxLength: 512,
          },
        },
        required: ['short_name'],
      },
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return value ('Account object with access_token') and that the token 'should be saved for future requests', which adds useful context about persistence needs. However, it lacks details on error conditions, rate limits, authentication requirements, or side effects (e.g., whether this creates a publicly visible account).

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 extremely concise (two sentences) and front-loaded with the core purpose. Every sentence earns its place: the first states the action and resource, the second explains the return value and critical follow-up action. There is zero wasted verbiage.

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

Completeness3/5

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

Given the tool's moderate complexity (account creation with 3 parameters) and no annotations or output schema, the description is minimally adequate. It covers the basic purpose and return value but lacks details on usage context, error handling, or behavioral nuances. For a creation tool with no structured safety hints, more guidance would be beneficial.

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 description coverage is 100%, so the schema fully documents all three parameters (short_name, author_name, author_url) with their constraints. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

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 description clearly states the specific action ('Create a new Telegraph account') and resource ('Account object'), distinguishing it from sibling tools like 'telegraph_edit_account_info' (which modifies existing accounts) or 'telegraph_get_account_info' (which retrieves account data). The verb 'Create' is precise and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether an existing account is needed), compare it to similar tools like 'telegraph_create_from_template', or specify use cases (e.g., initial setup vs. creating additional accounts).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NehoraiHadad/telegraph-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server