Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Set user properties

openpanel_set_user_properties
Destructive

Update properties on an existing user profile by specifying the site, profile ID, and property values. Use it to keep profile data current in OpenPanel.

Instructions

[UNIFIED] Update properties for an existing user profile.

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>",
      "profile_id": "<profile_id>",
      "properties": "<properties>"
    },
    "name": "openpanel_set_user_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
profile_idYes
propertiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already disclose that this is non-readonly, non-idempotent, and destructive. Beyond that, the description only confirms the target is an existing profile; it does not explain whether properties are merged or replaced, what happens to omitted properties, required permissions, or failure behavior for a destructive mutation.

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?

The description is a single compact sentence with no redundant wording. The "[UNIFIED]" prefix is unexplained noise, but it does not obstruct the sentence.

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

Completeness2/5

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

For a destructive mutation with three required parameters, a nested properties object, and no output schema, this one-line description is not complete enough. It identifies the action and target but omits parameter formats, merge semantics, and expected response or failure behavior.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it adds little: it does not define the site, profile_id, or the expected shape of the properties object. At most, it implies that properties belong to a user identified by profile_id, leaving the rest to inference from parameter names.

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 states a specific verb and resource: updating properties for an existing user profile. It also scopes the operation to an existing profile, which helps distinguish it from creation, though it does not explicitly name alternatives like openpanel_identify_user.

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 phrase "existing user profile" implies this should be used when the profile already exists, giving minimal usage context. However, it does not state prerequisites, when not to use it, or direct the agent to an alternative such as an identify/create tool.

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

Deploy Server

Other Tools