Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_hub_profile

Create a new hub profile in a target workspace, with options for visibility, URL, widgets, and action buttons.

Instructions

Create a new hub profile in a workspace.

workspace_id: target workspace ID — get available IDs from list_workspaces()
availability_level: "Public" (default) or "Private"
primary_url: optional external URL shown on the profile
app_clip_on: enable iOS App Clip
widgets: profile widget configuration objects
buttons: action buttons, each
    {"title": "...", "logic": {"type": "...", "url": "..."}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
buttonsNo
widgetsNo
sub_nameNo
user_nameYes
app_clip_onNo
descriptionNo
primary_urlNo
workspace_idYes
availability_levelNoPublic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.18

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior; the description adds no side-effect or permission details but also does not contradict the annotations.

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 well-organized as a compact parameter list with a useful example for buttons; it is concise but somewhat redundant with the schema's titles.

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?

Critical required parameters like name and user_name are not semantically explained, and the loose widget/button object structures are only partially described, making correct invocation uncertain.

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?

The description clarifies workspace_id, availability_level, primary_url, app_clip_on, widgets, and buttons, but leaves required fields name and user_name, plus sub_name and description, unexplained.

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?

The description states a specific action ('Create a new hub profile in a workspace') with a clear resource, and the verb 'create' distinguishes it from sibling update/get/delete/archive tools.

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 description implies usage for creating new hub profiles, but it does not explicitly contrast with alternatives like update_hub_profile or mention when not to use this 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