Skip to main content
Glama

ugc-pocket

by com.ugcpocket

List my campaigns (creator)

list_my_campaigns
Read-onlyIdempotent

For CREATOR API keys: lists the campaigns you are selected on (accepted application), with campaign_id, title, status, payment trigger and budget. Use the campaign_id with submit_posted_video to attach your published videos. Requires a creator API key (creator:submit scope) — generated in the UGC Pocket app under Settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignsNo

TDQS

A4.7/5.0
Behavior5/5

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

The description adds valuable context beyond the annotations by detailing the required creator API key scope (creator:submit), the filter of accepted applications, and the output fields. This complements the readOnlyHint and idempotentHint without contradiction.

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 concise, consisting of three short sentences that are front-loaded with the purpose. Every sentence provides essential information 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?

For a tool with no parameters and an output schema, the description fully covers the purpose, the creator-only scope, authentication requirements, and the follow-up action with submit_posted_video. It is complete and self-sufficient.

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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameters, and it correctly does not attempt to. It does mention output fields, but that is not parameter semantics.

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 lists the campaigns the creator is selected on (accepted applications), with specific fields returned. This distinguishes it from sibling tools like check_campaign_status and list_my_deliverables.

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?

It specifies the tool is for CREATOR API keys and explains how to use the resulting campaign_id with submit_posted_video. However, it does not explicitly mention alternatives or when not to use the tool, so it stops short of a 5.

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

All ugc-pocket toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation4/5

Most tools have distinct purposes, but create_campaign_draft and create_campaign_order both create campaign drafts, differentiated only by whether an API key exists. The descriptions help, but an agent could still be uncertain which to invoke.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (check_campaign_status, create_campaign_draft, list_my_campaigns, etc.). Modifiers like 'my' or 'posted' are consistently applied, so the naming is predictable and uniform.

Tool Count5/5

8 tools is well-scoped for a UGC campaign platform, covering both brand-side (create, estimate, check status) and creator-side (list campaigns, submit videos, track deliverables) workflows without unnecessary bloat or sparseness.

Completeness4/5

The tool set covers the main lifecycle: brand creates and monitors campaigns, creators discover and submit work, and deliverables are tracked. Minor gaps exist, such as no brand-side list of campaigns and no update/delete operations, but these are not critical dead ends.

Resources