UGC Pocket

Get service info

get_service_info

Read-onlyIdempotent

Returns what UGC Pocket does, the creator categories and platforms a draft can target, the price model and what happens after a draft. No authentication. Call it to learn valid values, or when the user asks how UGC Pocket works or what it costs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`mcp`	No
`docs`	No
`name`	No
`tools`	No
`paused`	No
`contact`	No
`openapi`	No
`pricing`	No	The price model, to relay as is.
`currency`	No
`platforms`	No
`categories`	No
`budget_unit`	No
`description`	No
`order_model`	No
`how_it_works`	No	What happens after a draft, to tell the user.
`max_campaign_budget_cents`	No
`min_campaign_budget_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 27, 2026

removedOutput schema / properties / api_key_signup
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / contact
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / how_it_works

Added value: +{
+  "description": "What happens after a draft, to tell the user.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / onboarding

Removed 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"
-}

addedOutput schema / properties / paused
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / prestations

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / pricing

Added value: +{
+  "description": "The price model, to relay as is.",
+  "type": "string"
+}

addedOutput schema / properties / tools

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely new context: 'No authentication' and a preview of what the service exposes. It stops short of anything like rate limits, but for a no-arg info tool this is solid.

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?

Two sentences, front-loaded with what is returned, then when to call it. No filler or redundancy; every clause adds information.

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?

An output schema exists, so return values need not be explained further, yet the description still summarizes the payload's categories. For a zero-arg, read-only discovery tool this is fully sufficient to invoke correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a zero-param tool is 4. No parameter-level guidance is needed or missing.

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 uses a specific verb ('Returns') and enumerates concrete resources: service purpose, creator categories, targetable platforms, price model, and post-draft behavior. Its discovery role is distinct from the write-oriented sibling create_campaign_draft, which an agent can infer without opening the schema.

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?

It gives explicit triggers: 'Call it to learn valid values' and 'when the user asks how UGC Pocket works or what it costs.' The 'learn valid values' clause also implicitly routes the agent here before invoking create_campaign_draft, covering the main decision the agent faces.

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?