Skip to main content
Glama

telegraph_list_templates

Retrieve available page templates and their fields to create structured Telegraph pages with consistent formatting.

Instructions

List all available page templates with their fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'telegraph_list_templates' tool. It calls listTemplates() from the templates module and returns the result as formatted JSON text content.
    if (name === 'telegraph_list_templates') {
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(listTemplates(), null, 2),
        }],
      };
    }
  • Tool definition including name, description, and empty inputSchema (no parameters required). Part of the templateTools array.
    {
      name: 'telegraph_list_templates',
      description: 'List all available page templates with their fields',
      inputSchema: {
        type: 'object' as const,
        properties: {},
      },
    },
  • Imports templateTools (containing 'telegraph_list_templates') and handleTemplateTool, then registers it in the combined allTools export for the MCP server.
    import { templateTools, handleTemplateTool } from './templates.js';
    import { exportTools, handleExportTool } from './export.js';
    
    // Export all tool definitions
    export const allTools = [...accountTools, ...pageTools, ...templateTools, ...exportTools];
  • Helper function listTemplates() that returns a list of all available templates with their metadata (name, description, fields), used by the tool handler.
    export function listTemplates(): Array<{name: string; description: string; fields: TemplateField[]}> {
      return Object.values(templates).map(t => ({
        name: t.name,
        description: t.description,
        fields: t.fields,
      }));
    }
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 mentions that templates include 'their fields', which hints at the return structure, but doesn't describe other behaviors like pagination, rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps.

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 function without any fluff. 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.

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is adequate but not fully complete. It lacks details on return format (e.g., structure of template data), error handling, or prerequisites. With no annotations or output schema, more context would be helpful for reliable use.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description adds no parameter information, which is appropriate here. Baseline for 0 parameters is 4, as there's nothing to compensate for, and the description doesn't mislead about inputs.

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 ('List') and the resource ('all available page templates with their fields'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'telegraph_get_page_list' (which likely lists actual pages rather than templates), but the mention of 'templates' provides some implicit distinction.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used before 'telegraph_create_from_template' or how it relates to 'telegraph_get_page_list'. The description only states what it does, not when it's appropriate.

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