Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

Use this when you need to see the founder's projects, or to turn a name they used ("the iOS beta") into the prj_… handle most other tools need. It lists the projects in this workspace, newest first. A project is one launch: its own audience, forms, hosted pages and settings. If the API key is pinned to a single project, this returns exactly that one. Not for one project's forms, stages or numbers (use get_project) or for making one (use create_project).

It pages with starting_after: pass the next_cursor from the previous response. When has_more is false there is nothing left to fetch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many projects to return, 1-50. Defaults to 20.
starting_afterNoA `prj_…` handle from a previous page; returns the projects after it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: newest-first ordering, what a project contains (audience, forms, hosted pages, settings), and the pinned-key short-circuit. It doesn't discuss result size or error behavior, keeping it short of a 5.

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?

Front-loaded with the primary trigger, then the concept definition, then exclusions, then the paging loop as a separate paragraph. Every sentence carries either selection guidance or a calling convention; nothing is redundant with the schema or annotations.

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

Completeness5/5

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

For a two-optional-parameter list tool with no output schema, the description covers trigger, exclusions, ordering, scope constraining, and the full pagination loop. Nothing an agent needs to call it correctly and terminate paging is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description goes further by explaining the pagination contract around `starting_after` — feed it the `next_cursor` from the prior response and stop when `has_more` is false. That adds operational meaning the schema alone ('a handle from a previous page') does not fully convey.

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?

States a specific verb and resource ('lists the projects in this workspace') plus a second concrete use case: resolving a spoken name like "the iOS beta" into a `prj_…` handle. It explicitly distinguishes itself from `get_project` and `create_project`, so an agent can separate it from the sibling set without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('see the founder's projects', resolve a name to a handle) and explicit when-not-to-use with named alternatives (`get_project` for one project's forms/stages/numbers, `create_project` for creation). It also documents the pinned-API-key edge case where exactly one project is returned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.