PixelGlass

Take a member out of a circle

remove_from_circle

Idempotent

On one site of the account, named in site. Takes the member — by their address, or their app's id — out of a circle; the posts for it lock for them again. A member not in it stays as they are.

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": {
      "site": "<site>",
      "circle": "<circle>",
      "member": "<member>"
    },
    "name": "remove_from_circle"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	The site to work on, as list_sites names it
`circle`	Yes	The circle's id, slug or name
`member`	Yes	The member's address, or their app's id

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnly=false, destructive=false, idempotent=true and openWorld=true, so the bar is lower, but the description still adds real context beyond them: the effect on the member ('the posts for it lock for them again') and the no-op outcome for non-members, which substantiates the idempotent hint. It does not say whether the removal is reversible by re-adding or what permissions are required, and nothing here contradicts 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?

Two short sentences with the site scoping front-loaded and the side effect and no-op case trailing. Slightly idiomatic phrasing ('lock for them again') costs a little precision but nothing is wasted.

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 three-parameter, fully documented mutation with annotations present and no output schema, the description supplies the key behavioral facts an agent needs: the site scope, the post-access consequence, and the no-op condition. Permission requirements and reversibility are the only notable omissions.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents site, circle and member. The description restates the same facts ('named in site', 'by their address, or their app's id') without adding format, matching or resolution details, so baseline 3 applies.

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 ('Takes ... out of') and resource ('a circle'), plus the scope constraint that it applies to one site named in the site parameter. It is immediately distinguishable from add_to_circle and remove_member_label in the sibling list.

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?

Usage is implied rather than stated: the tool removes a member from a circle, and the closing sentence describes the no-op case when the member is not in the circle. It never names add_to_circle as the alternative for the reverse operation, nor states prerequisites such as needing the member to already exist on the site.

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

All PixelGlass 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?