Skip to main content
Glama

Cloud Marketplace Manage Tool

marketplace_manage

Manage cross-team marketplace listings: browse, publish, install, and review shared skills, agents, and workflows. View install analytics for your published items.

Instructions

Cross-team marketplace for shared skills, agents, and workflows. browse and categories are public (no auth scope); publish, install, review operate within the caller's team. Installing a listing copies the artifact into the team and increments the listing's install count.

Actions:

  • browse (read) — optional: query, category, sort. Public.

  • categories (read) — taxonomy of available categories. Public.

  • publish (write) — listing data: target_type (skill/agent/workflow), target_id, name, description, visibility (public/private/team).

  • install (write) — listing_slug. Copies the listed entity into your team.

  • review (write) — listing_slug, rating (1-5), comment. One review per user per listing.

  • analytics (read) — listing_slug. Install counts, ratings (publisher only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: browse, publish, install, review, categories, analytics
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
typeNoFilter by listing type (e.g. skill, agent, workflow)
limitNoMax results to return (default 10, max 100)
entity_typeYesType of entity to publish: skill, agent, workflow, or bundle
entity_idNoUUID of the entity to publish (not required for bundle)
bundle_itemsNoFor bundle type: array of {type, id} objects. e.g. [{"type":"skill","id":"uuid"},{"type":"agent","id":"uuid"}]
nameNoMarketplace listing name (required for bundle)
descriptionNoMarketplace listing description
visibilityNoListing visibility: public (all users), unlisted (direct link only), team (team members only). Default: publicpublic
listing_slugYesThe marketplace listing slug
ratingYesRating from 1 (poor) to 5 (excellent)
commentNoOptional review comment (max 1000 characters)
listing_idNo
Behavior5/5

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

With empty annotations, the description fully discloses behavioral traits: public vs team-scoped actions, install side-effects (copy artifact, increment count), review constraints (one per user per listing), and analytics limited to publisher. No contradictions 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.

Conciseness4/5

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

The description is moderately long but well-structured with bullet points for each action. Every sentence contributes useful information. Minor redundancy in action listings but overall efficient.

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?

No output schema exists, but the description does not specify return values for actions like browse or publish. For a tool with 14 parameters and 6 actions, more details on expected outputs would improve completeness.

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 high (93%), and the description adds value by grouping parameters under actions and explaining constraints (e.g., bundle_items format, visibility defaults). However, it does not describe every parameter in detail beyond the schema.

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 clearly states the tool is a 'Cross-team marketplace for shared skills, agents, and workflows' and lists specific actions (browse, publish, install, etc.) with brief explanations. It distinguishes itself from sibling tools (e.g., admin_manage, agent_manage) by explicitly describing marketplace functionality.

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

Usage Guidelines4/5

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

The description provides clear context for when to use different actions: 'browse and categories are public', others operate within the caller's team. It also notes that installing copies artifacts and increments count. However, it does not explicitly state when to avoid the tool or suggest alternatives for similar tasks.

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/escapeboy/agent-fleet-o'

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