Skip to main content
Glama

List project items

list_project_items
Read-onlyIdempotent

List one kind of item in a project, by name and metadata only; no secret value, password or file content ever comes back (item secrets carries each key's note) (reveal_values or pull_env return those). item environments: id, slug, kind and key count per environment; one outside this token's limits is marked restricted with no count. item secrets (environment required): keys sorted by name with kind, note, version and last change; plain (non-secret) entries carry their value, and keys this token cannot open are flagged protected, sealed or restricted. item files: id, name, size, content type, environment and upload time, newest first; without environment, the project-level files plus those of every environment this token reaches. item logins: id, name, URL and username, sorted by name. item deployment_urls: id, label, URL, primary flag and environment. item members: people with their role (owner, editor, reader), whether they see only shared items, and since when; members change only in the web app. To find a key across projects or test exact names use find_secret_keys. Read-only. Requires projects:read, or logins:read for logins; members and files also need full access to the project. Paginated (secrets, files, logins): pass nextCursor back as cursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "item": "<item>"
    },
    "name": "list_project_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesWhat to list
limitNosecrets, files, logins only: items per page, 1 to 200. Default 100.
cursorNosecrets, files, logins only: the nextCursor of the previous page
searchNosecrets, files, logins only: case-insensitive substring filter, applied before paging
projectYesProject slug or id
environmentNosecrets: required, the environment whose keys to list. files: optional, only that environment's files. Ignored otherwise

Output Schema

NameRequiredDescriptionDefault
urlsNo
filesNo
loginsNo
membersNo
projectNo
secretsNo
nextCursorNoPass as cursor to read the next page; null at the end
environmentNo
environmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / urls / items / properties / id / description
      Previous value: -"Pass to update_deployment_url or delete_deployment_url"New value: +"Pass as url_id to manage_project_details action update_url or delete_item item deployment_url"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses that no secret values, passwords or file content are ever returned, which kinds are paginated, sort orders (name for secrets/logins, newest first for files), and that out-of-scope items are marked restricted/protected/sealed. It also spells out the permission requirements (projects:read, logins:read, full project access for members/files). The only gap is that it does not describe response envelope or error behavior, but the output schema covers return shape.

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?

Purpose is front-loaded, then a per-item breakdown, then alternatives, permissions and pagination. Every sentence carries information, but the semicolon-dense run-on phrasing and stray parenthetical ('(item secrets carries each key's note)') make it harder to scan than it needs to be.

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 six-mode list tool with an output schema, the description covers mode semantics, permissions, ordering, pagination and value-visibility constraints. Nothing an agent needs in order to choose and call this 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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by adding meaning the schema lacks, notably that files without an environment return project-level files plus those of every reachable environment, and that cursor must be the nextCursor of the prior page. It largely restates the schema's environment and pagination notes rather than adding new detail, keeping it short of a 5.

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 ('List one kind of item in a project') and then enumerates all six item kinds with the fields each returns. It explicitly separates itself from siblings by noting that reveal_values or pull_env return secret values and find_secret_keys searches across projects.

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?

Names alternatives and the conditions that select them: use find_secret_keys to search across projects or test exact names, use reveal_values/pull_env to get secret values, and note that members can only be changed in the web app. It also states that environment is required for secrets and ignored for other kinds.

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