Skip to main content
Glama

cf_list_access_apps

Retrieve a list of Cloudflare Access apps for an account using auto-paginated API calls. Returns app IDs, names, domains, and key configuration details.

Instructions

List Cloudflare Access applications configured at the account.

Calls: GET /accounts/{account_id}/access/apps (auto-paginated).

Returns: envelope with `data = {apps: [...], count, account_id}`.

**Compact projection**: each app is reduced to {id, name, domain, type,
session_duration, auto_redirect_to_identity, aud, created_at, updated_at}.
Cloudflare returns a much larger payload per app (policies, allowed_idps,
cors_headers, custom_pages, http_only_cookie_attribute, etc.) — at 50
apps × ~3.7KB this blows the 20K-token response ceiling. For full app
config, call `cf_get_access_app(account_id, app_id)`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNo
max_pagesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses auto-pagination, the envelope structure, and the compact projection to avoid token limits. With no annotations, this provides adequate transparency about the tool's behavior and limitations.

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, starting with the main purpose, then endpoint, return structure, and important note. It is not overly verbose, but the parameter section could be more compact.

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?

Given the tool has an output schema and only two parameters (none required), the description provides sufficient context: the envelope, compact projection, and guidance on avoiding token limits. It could mention max_pages but is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only indirectly explains account_id via the API endpoint. The max_pages parameter is not explained at all, leaving the agent without critical usage details for pagination control.

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 Cloudflare Access applications configured at the account' with a specific verb and resource. It distinguishes from the sibling tool cf_get_access_app by noting that this tool returns a compact projection and that the other should be used for full app config.

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 clear context: it is used to list all applications, and it explicitly suggests using cf_get_access_app for full configuration details. However, it does not explicitly state when not to use this tool or mention any prerequisites.

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/wojtekkura/cf-mcp'

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