Skip to main content
Glama

telegraph_get_account_info

Retrieve Telegraph account details including author name, URL, and page count using an access token. Specify which account fields to return for customized information.

Instructions

Get information about a Telegraph account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYesAccess token of the Telegraph account
fieldsNoList of account fields to return (default: short_name, author_name, author_url)

Implementation Reference

  • The handler logic for the 'telegraph_get_account_info' tool. It validates the input using GetAccountInfoSchema, calls the telegraph.getAccountInfo function, and returns the result as JSON text.
    case 'telegraph_get_account_info': {
      const input = GetAccountInfoSchema.parse(args);
      const result = await telegraph.getAccountInfo(
        input.access_token,
        input.fields as AccountField[] | undefined
      );
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(result, null, 2),
        }],
      };
    }
  • Zod schema for input validation of the telegraph_get_account_info tool, defining access_token and optional fields.
    export const GetAccountInfoSchema = z.object({
      access_token: z.string().describe('Access token of the Telegraph account'),
      fields: z.array(z.enum(['short_name', 'author_name', 'author_url', 'auth_url', 'page_count']))
        .optional()
        .describe('List of account fields to return'),
    });
  • Registration of the 'telegraph_get_account_info' tool in the accountTools array, including name, description, and input schema definition.
    {
      name: 'telegraph_get_account_info',
      description: 'Get information about a Telegraph account.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          access_token: {
            type: 'string',
            description: 'Access token of the Telegraph account',
          },
          fields: {
            type: 'array',
            items: {
              type: 'string',
              enum: ['short_name', 'author_name', 'author_url', 'auth_url', 'page_count'],
            },
            description: 'List of account fields to return (default: short_name, author_name, author_url)',
          },
        },
        required: ['access_token'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets' information, implying a read-only operation, but doesn't cover aspects like authentication needs (implied by the access_token parameter), rate limits, error handling, or response format, which are critical for a tool with no output schema.

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 a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It lacks details on behavioral traits, response format, and usage context, which are essential for an agent to invoke it correctly without structured output information.

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 input schema has 100% description coverage, clearly documenting both parameters and their purposes. The description adds no additional meaning beyond what the schema provides, such as explaining default behavior or usage examples, so it meets the baseline for high schema coverage without compensating value.

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 verb ('Get') and resource ('information about a Telegraph account'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'telegraph_get_page' or 'telegraph_get_page_list' beyond the resource type, 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 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. With siblings like 'telegraph_edit_account_info' for updates or 'telegraph_get_page' for page-specific data, there's no mention of context, prerequisites, or exclusions, leaving usage unclear.

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