Skip to main content
Glama

Visibility Genies

List projects

list_projects
Read-only

Lists the projects you can work in. It buys no data and uses no credits. Call it whenever another Visibility Genies tool needs a projectId: use the id of the project you want. Each project has {id, name, domain, locationCode, languageCode, clientId, clientName}. locationCode and languageCode are the project's default market, which tools use when a call leaves location and language out. clientId and clientName give the client the project is grouped under (see list_clients), or null. If you belong to several organizations, each project also names its organization and organizationId (pass that to create_project). Projects that other accounts shared with you are listed as well, each with shared {ownerAccount, level}: the level (view, work, work_and_spend) is what you may do there, and its paid tools are charged to the owner's account, within the owner's agent spend limit.

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

Output Schema

NameRequiredDescriptionDefault
metaNo
projectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavior beyond that: zero credit/data cost, inclusion of projects shared by other accounts, the view/work/work_and_spend permission levels, and the fact that paid tools on shared projects bill to the owner's account within the owner's spend limit. These are exactly the operational facts an agent cannot derive from structured fields.

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?

Front-loaded with purpose and the cost/no-credit reassurance, then progressively deeper detail about shared projects. It is dense but every sentence carries operational weight; the enumeration of returned fields is the only portion approaching redundancy given an output schema exists.

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 zero-parameter read-only list tool with an output schema, the definition covers purpose, trigger condition, cost, and the semantics of the returned identifiers and shared-project fields. Return-field enumeration overlaps with the output schema, but nothing an agent needs to call it correctly 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?

The tool takes zero parameters, so the baseline is 4; the description cannot document inputs it does not have. It does add downstream meaning by explaining what to extract from the result (the id) and what locationCode/languageCode default to when a later call omits those values.

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 you can work in') and immediately scopes it by relevance to other tools. It distinguishes itself from list_clients and create_project by explaining the id/clientId relationship, so an agent can tell what this tool is for 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 Guidelines4/5

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

Gives an explicit trigger: 'Call it whenever another Visibility Genies tool needs a projectId' and names which field to use ('use the id of the project you want'). It also removes a common hesitation by stating 'It buys no data and uses no credits.' No explicit when-not or archived-project alternative is named, so it stops short of a 5.

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