ugc-pocket

Get service info

get_service_info

Read-onlyIdempotent

Returns the UGC Pocket service descriptor: creator categories (e.g. dog, cooking, sport), prestation types, supported platforms, currency (EUR, budgets in cents), minimum and maximum campaign budget, the order model (agent creates a draft, a human confirms and funds it in the app), AND the "onboarding" object with the exact steps to give the user so they can create an account and generate an API key. No authentication required. Call this first to learn valid enum values, or whenever you need to tell a user how to connect UGC Pocket to their agent.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`mcp`	No
`docs`	No
`name`	No
`openapi`	No
`currency`	No
`platforms`	No
`categories`	No
`onboarding`	No	How a human creates an account and generates the API key. Relay these steps to the user verbatim; an agent cannot sign up on its own.
`budget_unit`	No
`description`	No
`order_model`	No
`prestations`	No
`api_key_signup`	No
`max_campaign_budget_cents`	No
`min_campaign_budget_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 4, 2026

addedOutput schema / properties / max_campaign_budget_cents
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / onboarding

Added value: +{
+  "description": "How a human creates an account and generates the API key. Relay these steps to the user verbatim; an agent cannot sign up on its own.",
+  "type": "object"
+}

Changed2 schema fields changedJul 14, 2026
- removedOutput schema / properties / min_budget_per_creator_cents
```
Removed value: -{
-  "type": "integer"
-}
```
- addedOutput schema / properties / min_campaign_budget_cents
```
Added value: +{
+  "type": "integer"
+}
```
First observedJul 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint true, and the description adds 'No authentication required,' a useful behavioral detail not captured by annotations. It also describes the order model context, but without more depth on potential side effects (though none apply here).

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 efficient: a single structured sentence listing key contents, followed by two short sentences on authentication and usage. It is front-loaded with the main verb and resource, and every clause adds value without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (no inputs) and the presence of an output schema, the description is remarkably complete. It covers what data is returned, the order model, onboarding steps, and when to call it, leaving no gaps for the agent.

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?

The tool has zero parameters, so the schema provides no parameter descriptions. Per the rubric, 0 params earns a baseline of 4. The description focuses on output details rather than parameters, which 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 clearly states the tool's purpose: 'Returns the UGC Pocket service descriptor' and enumerates specific contents like creator categories, platforms, currency, budgets, order model, and onboarding steps. It distinguishes from sibling tools by framing itself as the first call for enum values and account setup.

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

Usage Guidelines5/5

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

Provides explicit usage guidance: 'Call this first to learn valid enum values, or whenever you need to tell a user how to connect UGC Pocket to their agent.' This tells the agent exactly when to invoke it, and implicitly contrasts with sibling campaign-related tools.

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

All ugc-pocket tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?