Skip to main content
Glama

project_templates_list

List project templates to reuse predefined project structures. Use cursor-based pagination to browse available templates for standardizing project creation.

Instructions

List all project templates with cursor-based pagination.

Project templates are reusable blueprints for creating new projects with predefined phases, tasks, and activities.

Workflow tips:

  • Templates include project structure (phases, groups, tasks, activities)

  • Use templates to standardize project creation across your organization

  • Templates can be created from existing projects

  • Cursor-based pagination for large template lists

Common use cases:

  • List all available templates: {}

  • Get templates with custom page size: { "limit": 50 }

  • Paginate through templates: { "cursor": "abc123", "limit": 100 }

Example: { "limit": 100 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoFor pagination, the marker representing the first item on the next page
limitNoNumber of items to return per page (default: 100, max: 500)
Behavior4/5

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

Since no annotations are provided, the description fully covers behavioral traits: cursor-based pagination, default/max limit, and that templates contain predefined structure. It clearly indicates a read-only operation overall.

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

Conciseness4/5

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

The description is well-structured with a clear first line, bullet points, and examples. It is not overly long, though the example partially repeats limit defaults, which is slightly redundant but not harmful.

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 simple list tool without an output schema, the description adequately covers pagination behavior, template structure, and common use cases. No critical gaps are evident.

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 already describes both parameters (cursor, limit) with 100% coverage. The description adds examples and context but does not provide new semantic meaning beyond what the schema offers, making a baseline score of 3 appropriate.

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 'List all project templates with cursor-based pagination', specifying the verb (List), resource (project templates), and pagination method. This distinguishes it from sibling tools like project_templates_get and projects_list, which serve different purposes.

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?

The description provides workflow tips and common use cases, explaining when to use templates (e.g., 'standardize project creation') and includes pagination examples. However, it does not explicitly state when not to use this tool or mention alternatives.

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/iamsamuelfraga/mcp-pipedrive'

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