Boomerang

Update workspace member

update_workspace_member

Idempotent

Update an existing workspace member's profile settings. member_profile ONLY accepts super_connector_settings (onboarding status, connection consent, opportunity stage, contact seniority, minimum deal size) — email, first_name, and last_name are rejected because identity belongs on the User entity. Does not change workspace roles — use add_role or remove_role for role changes.

Use when: Use when an admin needs to update Super Connector profile settings for an existing workspace member. The member record must already exist. For role changes use add_role or remove_role.

Behavior: idempotent

workspace_id / user_id are injected from request headers.

Also returns pagination info (created_at, updated_at, created_by, updated_by, deleted_at, deleted_by).

Input Schema

Name	Required	Description	Default
`member_profile`	No
`keycloak_user_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

removedInput schema / properties / _triggered_by

Removed value: -{
-  "default": "",
-  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
-  "type": "string"
-}

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare idempotentHint, destructiveHint=false, and openWorldHint=false, so the description's 'idempotent' restatement is redundant. It earns credit by adding behavior beyond the annotations: the exact field-acceptance/rejection rules for member_profile, the fact that identity fields belong on the User entity, and that workspace_id/user_id are injected from request headers.

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?

Front-loaded with purpose, then constraints, then usage, behavior, and return info — a sensible ordering. It is slightly redundant (the 'idempotent' trait duplicates the annotation and the role-change warning appears twice), which keeps it from a 5, but no sentence is wasteful.

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 an output schema exists, the return-value sentence is not strictly needed but is harmless. Annotations cover the safety profile and the description covers field semantics and header injection, so an agent has what it needs; the only gap is the unexplained keycloak_user_id parameter.

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 0%, so the description carries the burden, and it does so well for member_profile: it enumerates the accepted super_connector_settings (onboarding status, connection consent, opportunity stage, contact seniority, minimum deal size) and the rejected fields. It falls short of full compensation because keycloak_user_id is never mentioned in the description or schema.

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 ('Update an existing workspace member's profile settings') and immediately scopes it against siblings by declaring what member_profile does and does not accept, plus that identity fields are rejected. An agent can distinguish this from create_workspace_member, merge_workspace_members, and update_user_profile without opening a schema.

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?

Provides an explicit 'Use when' clause (admin updating Super Connector profile settings for an existing member), a precondition ('The member record must already exist'), and names the alternatives for the excluded case ('For role changes use add_role or remove_role'). When-to-use, when-not, and alternatives are all present.

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

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