Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

Projects (a product or client) that scope chats, brand profiles and content. Includes the brand brief agents are briefed from.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint and idempotentHint annotations already establish a side-effect-free, repeatable read, while the description adds that the result includes the brand brief. It does not disclose whether the listing covers all accessible projects, how access is determined, or whether results are paginated or ordered.

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 two short fragments are information-dense and front-load the definition of a project without repeating annotations or schema. A verb-led opening would be more direct, and 'brand brief agents are briefed from' is slightly awkward, so the wording is not maximally polished.

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?

For a simple zero-input read, the domain definition and brand-brief inclusion are enough for basic selection and invocation. With no output schema, however, the absence of listing scope, pagination details, and the broader result shape leaves noticeable gaps for interpreting and using the response.

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?

There are no documented parameters, so the zero-parameter baseline applies and no input semantics require elaboration. The description also does not suggest unsupported filters or options.

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?

Together with the name and title, the description makes the resource clear: projects represent products or clients and scope chats, brand profiles, and content. The brand-brief detail adds useful context, but the description itself has no list verb and does not explicitly distinguish this tool from siblings such as list_plans or list_planner_campaigns.

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 project-scoping and brand-brief language implies using the tool to discover project context before related work. It never explicitly states when to choose it, when not to use it, or which alternative to use for a different need.

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.

Resources