Skip to main content
Glama

user

Destructive

User profile, contacts, invitations, and assets. Call action='describe' for the full action/param reference. Destructive: close.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return (1-500, default 100)
queryNoContact search substring.
actionYesOperation. Use 'describe' for full action reference.
offsetNoNumber of items to skip (default 0)
contentNoPlain text content for asset upload.
user_idNo19-digit user ID or email.
archivedNoTrue for archived shares, false for active.
filenameNoOriginal filename.
last_nameNoFamily name.
asset_nameNoAsset type name (e.g. profile_pic).
first_nameNoGiven name.
confirmationNoEmail or user ID confirmation for account close.
content_typeNoMIME type.
display_limitNoHow many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to list-shares.
email_addressNoEmail address.
invitation_idNoInvitation opaque ID or key.
content_base64NoBase64-encoded binary content.
invitation_keyNoInvitation key.
describe_actionNoWhen action='describe', narrow the output to ONE action's full params/notes (e.g. 'me'). Omit to get the compact action index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / display_limit / description
      Previous value: -"How many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to…"New value: +"How many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to list-shares."
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "describe",
      -  "me",
      -  "update",
      -  "search-contacts",
      -  "close",
      -  "details-by-id",
      -  "profiles",
      -  "allowed",
      -  "org-limits",
      -  "list-shares",
      -  "invitation-list",
      -  "invitation-details",
      -  "accept-all-invitations",
      -  "asset-upload",
      -  "asset-delete",
      -  "asset-types",
      -  "asset-list",
      -  "instructions-get",
      -  "instructions-set",
      -  "instructions-clear"
      -]New value: +[
      +  "describe",
      +  "me",
      +  "update",
      +  "search-contacts",
      +  "close",
      +  "details-by-id",
      +  "profiles",
      +  "allowed",
      +  "org-limits",
      +  "list-shares",
      +  "invitation-list",
      +  "invitation-details",
      +  "accept-all-invitations",
      +  "asset-upload",
      +  "asset-delete",
      +  "asset-types",
      +  "asset-list"
      +]
    • changedInput schema / properties / content / description
      Previous value: -"Plain text content (asset upload or instructions body, max 65536 bytes UTF-8 for instructions)."New value: +"Plain text content for asset upload."
  3. Changed2 schema fields changed
    • addedInput schema / properties / describe_action
      Added value: +{
      +  "description": "When action='describe', narrow the output to ONE action's full params/notes (e.g. 'me'). Omit to get the compact action index.",
      +  "type": "string"
      +}
    • changedInput schema / properties / display_limit / description
      Previous value: -"How many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to list-shares."New value: +"How many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to…"
  4. Changed12 schema fields changed
    • removedInput schema / properties / display_limit / anyOf
      Removed value: -[
      -  {
      -    "maximum": 500,
      -    "minimum": 1,
      -    "type": "integer"
      -  },
      -  {
      -    "pattern": "^-?\\d+$",
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / display_limit / maximum
      Added value: +500
    • addedInput schema / properties / display_limit / minimum
      Added value: +1
    • addedInput schema / properties / display_limit / type
      Added value: +"integer"
    • removedInput schema / properties / limit / anyOf
      Removed value: -[
      -  {
      -    "maximum": 500,
      -    "minimum": 1,
      -    "type": "integer"
      -  },
      -  {
      -    "pattern": "^-?\\d+$",
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / limit / maximum
      Added value: +500
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / limit / type
      Added value: +"integer"
    • removedInput schema / properties / offset / anyOf
      Removed value: -[
      -  {
      -    "maximum": 9007199254740991,
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "pattern": "^-?\\d+$",
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • addedInput schema / properties / offset / type
      Added value: +"integer"
  5. Changed25 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Operation to perform"New value: +"Operation. Use 'describe' for full action reference."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "me",
      -  "update",
      -  "search-contacts",
      -  "close",
      -  "details-by-id",
      -  "profiles",
      -  "allowed",
      -  "org-limits",
      -  "list-shares",
      -  "invitation-list",
      -  "invitation-details",
      -  "accept-all-invitations",
      -  "asset-upload",
      -  "asset-delete",
      -  "asset-types",
      -  "asset-list",
      -  "instructions-get",
      -  "instructions-set",
      -  "instructions-clear"
      -]New value: +[
      +  "describe",
      +  "me",
      +  "update",
      +  "search-contacts",
      +  "close",
      +  "details-by-id",
      +  "profiles",
      +  "allowed",
      +  "org-limits",
      +  "list-shares",
      +  "invitation-list",
      +  "invitation-details",
      +  "accept-all-invitations",
      +  "asset-upload",
      +  "asset-delete",
      +  "asset-types",
      +  "asset-list",
      +  "instructions-get",
      +  "instructions-set",
      +  "instructions-clear"
      +]
    • changedInput schema / properties / archived / description
      Previous value: -"True to show archived shares, false for active (used by: list-shares)"New value: +"True for archived shares, false for active."
    • changedInput schema / properties / asset_name / description
      Previous value: -"Asset type name (e.g. profile_pic) (required for: asset-upload, asset-delete)"New value: +"Asset type name (e.g. profile_pic)."
    • changedInput schema / properties / confirmation / description
      Previous value: -"User's email address or user ID as confirmation (required for: close)"New value: +"Email or user ID confirmation for account close."
    • changedInput schema / properties / content / description
      Previous value: -"Plain text content. For asset-upload: e.g. an SVG body, used instead of content_base64 for text-based assets. For instructions-set: full markdown body that replaces the personal AI instructions slot (max 65536 bytes UTF-8). (used by: asset-upload, instructions-set)"New value: +"Plain text content (asset upload or instructions body, max 65536 bytes UTF-8 for instructions)."
    • changedInput schema / properties / content_base64 / description
      Previous value: -"Base64-encoded file content (for binary files). Use content for text. (used by: asset-upload)"New value: +"Base64-encoded binary content."
    • changedInput schema / properties / content_type / description
      Previous value: -"MIME type (e.g. image/png) (used by: asset-upload)"New value: +"MIME type."
    • addedInput schema / properties / display_limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 500,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    {
      +      "pattern": "^-?\\d+$",
      +      "type": "string"
      +    }
      +  ],
      +  "description": "How many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to list-shares."
      +}
    • changedInput schema / properties / email_address / description
      Previous value: -"Updated email address (used by: update)"New value: +"Email address."
    • changedInput schema / properties / filename / description
      Previous value: -"Original filename (e.g. photo.png) (used by: asset-upload)"New value: +"Original filename."
    • changedInput schema / properties / first_name / description
      Previous value: -"Updated first name (used by: update)"New value: +"Given name."
    • changedInput schema / properties / invitation_id / description
      Previous value: -"Invitation opaque ID or invitation key (required for: invitation-details)"New value: +"Invitation opaque ID or key."
    • changedInput schema / properties / invitation_key / description
      Previous value: -"Optional invitation key for users without validated email (used by: invitation-list, accept-all-invitations)"New value: +"Invitation key."
    • changedInput schema / properties / last_name / description
      Previous value: -"Updated last name (used by: update)"New value: +"Family name."
    • addedInput schema / properties / limit / anyOf
      Added value: +[
      +  {
      +    "maximum": 500,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^-?\\d+$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / limit / maximum
      Removed value: -500
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
    • addedInput schema / properties / offset / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^-?\\d+$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / offset / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / offset / minimum
      Removed value: -0
    • removedInput schema / properties / offset / type
      Removed value: -"integer"
    • changedInput schema / properties / query / description
      Previous value: -"Name or email substring to search your contacts (people you've interacted with before). Returns {email: name} — no user_id. (required for: search-contacts)"New value: +"Contact search substring."
    • changedInput schema / properties / user_id / description
      Previous value: -"19-digit numeric user ID or email (required for: details-by-id, asset-upload, asset-delete, asset-list)"New value: +"19-digit user ID or email."
  6. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "me",
      -  "update",
      -  "search-contacts",
      -  "close",
      -  "details-by-id",
      -  "profiles",
      -  "allowed",
      -  "org-limits",
      -  "list-shares",
      -  "invitation-list",
      -  "invitation-details",
      -  "accept-all-invitations",
      -  "asset-upload",
      -  "asset-delete",
      -  "asset-types",
      -  "asset-list"
      -]New value: +[
      +  "me",
      +  "update",
      +  "search-contacts",
      +  "close",
      +  "details-by-id",
      +  "profiles",
      +  "allowed",
      +  "org-limits",
      +  "list-shares",
      +  "invitation-list",
      +  "invitation-details",
      +  "accept-all-invitations",
      +  "asset-upload",
      +  "asset-delete",
      +  "asset-types",
      +  "asset-list",
      +  "instructions-get",
      +  "instructions-set",
      +  "instructions-clear"
      +]
    • changedInput schema / properties / content / description
      Previous value: -"Plain text content (e.g. SVG). Use this instead of content_base64 for text-based assets. (used by: asset-upload)"New value: +"Plain text content. For asset-upload: e.g. an SVG body, used instead of content_base64 for text-based assets. For instructions-set: full markdown body that replaces the personal AI instructions slot (max 65536 bytes UTF-8). (used by: asset-upload, instructions-set)"
  7. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "me",
      -  "update",
      -  "search",
      -  "close",
      -  "details-by-id",
      -  "profiles",
      -  "allowed",
      -  "org-limits",
      -  "list-shares",
      -  "invitation-list",
      -  "invitation-details",
      -  "accept-all-invitations",
      -  "asset-upload",
      -  "asset-delete",
      -  "asset-types",
      -  "asset-list"
      -]New value: +[
      +  "me",
      +  "update",
      +  "search-contacts",
      +  "close",
      +  "details-by-id",
      +  "profiles",
      +  "allowed",
      +  "org-limits",
      +  "list-shares",
      +  "invitation-list",
      +  "invitation-details",
      +  "accept-all-invitations",
      +  "asset-upload",
      +  "asset-delete",
      +  "asset-types",
      +  "asset-list"
      +]
    • changedInput schema / properties / query / description
      Previous value: -"Search query (name or email) (required for: search)"New value: +"Name or email substring to search your contacts (people you've interacted with before). Returns {email: name} — no user_id. (required for: search-contacts)"
  8. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already note destructiveHint=true and readOnlyHint=false. The description adds the specific information that the 'close' action is destructive, naming the exact operation. It also points to 'describe' for more detail, which is useful transparency about how to learn behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact: two sentences that convey the tool's scope, the key action to invoke for reference, and the destructive hint. Every clause earns its place, with no redundancy or filler. The 'Destructive: close' note is specific and valuable.

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

Completeness3/5

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

This is a complex multi-action tool with 19 parameters, no output schema, and broad capabilities. The description provides a high-level overview and defers to describe, which partially mitigates the lack of action-specific details. However, it omits return-value expectations and tool-selection guidance relative to siblings, leaving gaps for agent decision-making.

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?

All 19 parameters have complete descriptions in the schema (100% coverage), so the description does not need to elaborate on them. It adds the hint to use describe for a full action/param reference, which is helpful but does not materially enhance parameter understanding beyond the schema. Baseline 3 is appropriate.

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 identifies the tool as covering user profile, contacts, invitations, and assets, which gives a clear resource scope. It lacks a specific verb for a single action but is appropriate for a multi-action hub. The instruction to call action='describe' helps the agent discover specifics, and the resource list differentiates it from sibling tools like 'invitation' and 'auth'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. The only directive is to call action='describe' for the full reference, which is a within-tool navigation aid, not a selection guideline. No exclusions or sibling comparisons are offered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources