Skip to main content
Glama
Sign In

PixelGlass

by co.pixelglass
OverviewDiscussionsAdmin

Add a label to a member

add_member_label
Idempotent

On one site of the account, named in site. Puts one label on the member — by their address, or the id the publication's app gave them at single sign-on. A label that does not exist is made; a name finds its label in any case. The member keeps their other labels, and the automations for the label start. A label the member has already changes nothing.

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>",
      "member": "<member>",
      "label": "<label>"
    },
    "name": "add_member_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site to work on, as list_sites names it
labelYesThe label's name, with no comma
memberYesThe member's address, or their app's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that a missing label is created as a side effect, that name matching is case-insensitive, that other labels are preserved, that label automations are triggered, and that re-adding an existing label is a no-op (consistent with idempotentHint=true). These are exactly the behavioral details an agent needs before mutating member state.

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?

Four short sentences, front-loaded with scope and then the mutation semantics; nothing is padded. The phrasing is terse to the point of being slightly clipped ("A label the member has already changes nothing"), but every sentence carries information.

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-required-parameter mutation with no output schema, the description covers creation side effects, idempotency, and automation triggering. It omits error cases (e.g., unknown site or member) and permission requirements, which would complete the picture.

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, but the description adds genuinely new meaning: the label name matches case-insensitively ("a name finds its label in any case") and will be created if absent, and the member may be addressed either by address or by the app's SSO id. These nuances are not in the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ("Puts one label on the member") and scopes it to a single site named in `site`. It is clearly distinct from the sibling remove_member_label by implication, but never names it or any other alternative explicitly.

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?

The site-scoping sentence ("On one site of the account, named in site") sets the operating context and the member identifier options hint at how to target a user. There is no explicit when-to-use versus remove_member_label or other label/membership tools, so guidance is implied rather than stated.

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

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