Skip to main content
Glama

telegraph_edit_account_info

Update Telegraph account details like name, author information, or profile link using an access token to manage your publishing identity.

Instructions

Update information about a Telegraph account. At least one optional parameter must be provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYesAccess token of the Telegraph account
short_nameNoNew account name (1-32 characters)
author_nameNoNew default author name (0-128 characters)
author_urlNoNew default profile link (0-512 characters)

Implementation Reference

  • Handler function for the 'telegraph_edit_account_info' tool. Validates input using EditAccountInfoSchema and calls the Telegraph API to edit account info, returning the result as JSON.
    case 'telegraph_edit_account_info': {
      const input = EditAccountInfoSchema.parse(args);
      const result = await telegraph.editAccountInfo(
        input.access_token,
        input.short_name,
        input.author_name,
        input.author_url
      );
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(result, null, 2),
        }],
      };
    }
  • Zod schema defining the input parameters for the 'telegraph_edit_account_info' tool, used for validation in the handler.
    export const EditAccountInfoSchema = z.object({
      access_token: z.string().describe('Access token of the Telegraph account'),
      short_name: z.string().min(1).max(32).optional().describe('New account name (1-32 characters)'),
      author_name: z.string().max(128).optional().describe('New default author name (0-128 characters)'),
      author_url: z.string().max(512).optional().describe('New default profile link (0-512 characters)'),
    });
  • Registration of the 'telegraph_edit_account_info' tool in the accountTools array, including name, description, and JSON input schema.
    {
      name: 'telegraph_edit_account_info',
      description: 'Update information about a Telegraph account. At least one optional parameter must be provided.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          access_token: {
            type: 'string',
            description: 'Access token of the Telegraph account',
          },
          short_name: {
            type: 'string',
            description: 'New account name (1-32 characters)',
            minLength: 1,
            maxLength: 32,
          },
          author_name: {
            type: 'string',
            description: 'New default author name (0-128 characters)',
            maxLength: 128,
          },
          author_url: {
            type: 'string',
            description: 'New default profile link (0-512 characters)',
            maxLength: 512,
          },
        },
        required: ['access_token'],
      },
    },
Behavior2/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 correctly indicates this is a mutation operation ('Update'), but fails to mention important behavioral aspects such as authentication requirements (implied by 'access_token' but not stated), whether changes are reversible, error handling, or what happens to unspecified fields. This leaves significant gaps for an agent to understand the tool's behavior.

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—just two sentences that directly state the tool's purpose and a key constraint. Every word earns its place with no redundancy or fluff. It's front-loaded with the main action and efficiently communicates essential information without unnecessary elaboration.

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

Completeness2/5

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

Given that this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't cover behavioral traits like authentication needs, side effects, or response format, which are critical for safe and effective use. The high schema coverage helps with parameters, but overall context for a write operation is lacking.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description adds minimal value beyond the schema by noting that at least one optional parameter must be provided, which clarifies a constraint not explicit in the schema. However, it doesn't provide additional context about parameter interactions or usage examples, so it meets the baseline for high schema coverage.

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 clearly states the action ('Update') and target ('information about a Telegraph account'), making the purpose immediately understandable. It distinguishes itself from siblings like 'telegraph_create_account' (creation vs. update) and 'telegraph_get_account_info' (read vs. write). However, it doesn't specify exactly what information can be updated, which prevents a perfect score.

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

Usage Guidelines3/5

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

The description provides some usage guidance by stating 'At least one optional parameter must be provided,' which helps avoid empty updates. However, it doesn't explicitly mention when to use this tool versus alternatives like 'telegraph_create_account' for new accounts or 'telegraph_get_account_info' for reading information. The guidance is implied rather than explicit.

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