fynk MCP

Attach account users to team

attach-account-users-to-team

DestructiveIdempotent

Add one or more account users as members of a team.

Use this tool when:

The user asks to add people to a team

Membership can give people access to the documents, templates, imports and automations assigned to the team, subject to their own permissions, so confirm who is being added when the user's request leaves room for doubt.

Existing members of the team are preserved. Use detach-account-users-from-team to remove members. Pass account_user_uuids from list-account-users, list-account-team-members (when copying members between teams), or the account-user uuids the user references.

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": {
      "team_uuid": "<team_uuid>",
      "account_user_uuids": "<account_user_uuids>"
    },
    "name": "attach-account-users-to-team"
  }
}

Input Schema

Name	Required	Description	Default
`team_uuid`	Yes	UUID of the team to add members to
`account_user_uuids`	Yes	UUIDs of the account users to add as members of the team

Output Schema

Name	Required	Description
`icon`	No	Icon identifier for the team (e.g. "UserGroupIcon")
`name`	No	Name of the team
`uuid`	No	Identifier for the team. Do not show to the user unless they ask for it
`_entity_type`	No	Only relevant for tooling. Do not show to the user

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description complements this by explaining the actual blast radius — membership grants access to documents, templates, imports and automations, subject to user permissions — and advises confirming the target users. It also reassures that existing members are preserved, consistent with the idempotent hint. Slightly more could be said about behavior when a user is already a member, but the safety profile is well covered.

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 the core action, then organized into a when-to-use list, a risk note, and a relationship/parameter note. Efficient overall, though the guidance block is slightly longer than strictly necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. The description covers purpose, trigger, side effects, the inverse sibling, and UUID sourcing — everything an agent needs to invoke this mutation correctly and safely.

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; the description goes beyond it by identifying provenance for account_user_uuids (list-account-users, list-account-team-members, or user-referenced UUIDs), which helps the agent source valid values rather than invent them.

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: 'Add one or more account users as members of a team.' This is clearly distinguishable from the inverse sibling detach-account-users-from-team, which the description names explicitly.

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 trigger ('The user asks to add people to a team'), names the alternative tool for the opposite operation, and tells the agent exactly where the required UUIDs come from (list-account-users, list-account-team-members, or user-supplied). Nothing is left to inference.

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

All fynk MCP 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?