Skip to main content
Glama
hellocoop

Hellō Admin MCP Server

Official
by hellocoop

hello_manage_app

Manage Hellō applications: create, read, update, generate secrets, and upload logos via data or URL.

Instructions

Manage Hellō applications - create, read, update, create secrets, and upload logos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the application (optional for: create, update - if not provided for create, will be generated from user name)
themeNoLogo theme - whether this is for light or dark mode (optional for: update_logo_from_data, update_logo_from_url, defaults to "light")
actionYesAction to perform: create (new app), read (get app), update (modify app), create_secret (generate secret), update_logo_from_data (set logo from base64 data), update_logo_from_url (set logo from URL)
pp_uriNoPrivacy Policy URI (optional for: create, update)
team_idNoID of the team that owns the application (optional for all actions - uses default team if not specified)
tos_uriNoTerms of Service URI (optional for: create, update)
logo_urlNoURL of the logo image to fetch and set (required for: update_logo_from_url)
client_idNoID of the OAuth client/application (optional for read - returns profile if omitted; required for: update, create_secret, update_logo_from_data, update_logo_from_url)
logo_dataNoBase64 encoded logo data (required for: update_logo_from_data)
device_codeNoWhether the application supports device code flow (optional for: create, update)
dev_wildcardNoAllow wildcard domain redirects in development environment (optional for: create, update)
dev_127_0_0_1NoAllow 127.0.0.1 redirects in development environment (optional for: create, update)
dev_localhostNoAllow localhost redirects in development environment (optional for: create, update)
dev_redirect_urisNoArray of allowed redirect URIs for development environment (optional for: create, update)
logo_content_typeNoMIME type of the logo data, e.g. "image/png" (required for: update_logo_from_data; auto-detected for: update_logo_from_url)
prod_redirect_urisNoArray of allowed redirect URIs for production environment (optional for: create, update)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. However, it only lists action names without describing side effects, idempotency, authentication requirements, or error conditions. The actions imply mutation for create/update/create_secret/logo actions and idempotency for read, but this is not explicit.

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 concise sentence that lists the core actions. It is front-loaded with the primary verb 'Manage' and the resource. While efficient, a slightly more structured format could improve readability.

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?

Given the complexity of 16 parameters and no output schema, the description provides a high-level summary but lacks details on required fields per action, error handling, and return values. It is minimally adequate.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no parameter information beyond what is in the schema, thus baseline score of 3 is appropriate.

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 specifies the resource 'Hellō applications' and lists distinct actions: create, read, update, create secrets, and upload logos. This clearly defines the tool's scope and purpose, and as there are no sibling tools, differentiation is not needed.

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 does not provide guidance on when to use this tool versus alternatives, nor does it help choose between the multiple actions. While action names are self-explanatory, explicit usage context is absent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hellocoop/admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server