Connections

Choose which Cloudflare account this workspace uses

connections_cloudflare_account

DestructiveIdempotent

Use this when a Cloudflare connection reaches more than one account (the OAuth picker lets a member tick several). action 'list' (default) answers the accounts by NAME, the ones already chosen, and needsChoice; when needsChoice is true, ASK the member which account this workspace uses, then call action 'choose' with accountId (or accountIds). Every Cloudflare call and deploy then defaults to the chosen account; a change to any other account answers with how to add that account. The account list can always be read. Never returns a token.

Input Schema

Name	Required	Description
`action`	No	list (default) or choose.
`person`	No	Linked person to run this call as (first name). Omit to run as the connection's holder.
`project`	No	Workspace to run this call in (id or name).
`instance`	No	Which Cloudflare connection when the workspace holds several (omit for the default).
`accountId`	No	The 32-character account id to choose.
`accountIds`	No	Several account ids to choose.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / person

Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[]
```

AddedOct 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations, the description discloses the persistence side effect (every Cloudflare call and deploy defaults to the chosen account), that the list is always readable, and that no token is ever returned. It does not explain why destructiveHint=true is set or what auth/permission requirements the choose action carries, leaving a small gap. There is no contradiction with the annotations.

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 trigger condition is front-loaded and the list-then-choose loop follows in logical order with no filler sentences. It is a dense run-on paragraph however, and the switching/fallback sentence could be tighter.

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 6-parameter, zero-required tool with no output schema, the description explains what 'list' yields (account names, the ones already chosen, needsChoice) and that tokens are excluded, which is the core decision loop an agent needs. It omits what 'choose' returns and when to set person/project/instance, so it is strong but not exhaustive.

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 adds real meaning: it establishes 'list' as the default action, introduces the needsChoice signal that gates the use of accountId/accountIds, and frames accountIds as the plural form of accountId. The person, project, and instance parameters are covered only by the schema, not the prose.

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 names a specific verb sequence (list, then choose) on a specific resource (the Cloudflare account used by this workspace), and the title states the intent plainly. It is clearly separable from the deploy/other Cloudflare sibling tools because the selection gate ('more than one account', 'needsChoice') is spelled out.

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?

It states the trigger condition (a Cloudflare connection reaching more than one account, OAuth picker with several ticked), the branch behavior for 'list' as the default, and the exact next step when needsChoice is true: ask the member, then call 'choose' with accountId or accountIds. It also tells the agent what to expect when the user asks for a different account ('answers with how to add that account').

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

All Connections tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?