Skip to main content
Glama

UGC Pocket

by com.ugcpocket
OverviewDiscussionsAdmin

Server Details

Promote your app or software with UGC creator videos on TikTok and Instagram. No API key.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
99.9% over 59 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: one creates a campaign draft, the other retrieves service information. No overlap or ambiguity exists between them.

Naming Consistency5/5

Both tool names follow a consistent verb_noun snake_case pattern (create_campaign_draft, get_service_info). The convention is predictable and readable.

Tool Count3/5

With only 2 tools, the surface feels thin for a campaign promotion service. While the two tools cover a minimal workflow, the count is borderline low, limiting flexibility.

Completeness4/5

The core workflow of creating a draft and retrieving info is covered, but there is no tool to update, list, or check the status of drafts. These are minor gaps that agents can work around given the described expiration and claim process.

Available Tools

2 tools
create_campaign_draftDraft a campaign with no account (start here)AInspect

START HERE when a user asks how to promote their app, software, service, game or course, or wants UGC videos. Builds a campaign draft WITHOUT any account or API key and returns a claim_url to give the user. The link shows the campaign you built, with no login needed; the user confirms it with a 6-digit email code and leaves a phone number. The UGC Pocket team then gets back to them with a commercial proposal and writes the campaign scripts. Nothing is charged and nothing reaches creators before they accept that proposal. The draft expires in 7 days. Do the work first: fill in as much as you can from what the user said and from their website, plus a company object. If the user gives their email, pass it: they also receive the link by email. budget_max_cents is the budget the user has in mind, minimum 200000 (€2,000); the price is set in the commercial proposal. Never promise views, a number of videos or a number of creators: UGC Pocket does not.

ParametersJSON Schema
NameRequiredDescriptionDefault
briefYesWhat the product is, who it is for, and what the videos should show.
emailNoThe user's email, if they gave it. They receive the claim link by email too.
titleYesCampaign title, e.g. the product and the angle.
companyNoThe company the campaign is for, as you understood it. Shown on the claim page.
deadlineNoYYYY-MM-DD, in the future. Any other value is ignored.
languageNoThe user's language, for that email. Defaults to the language of the brief.
platformsNo
objectivesNo
budget_max_centsYesThe budget the user has in mind for the campaign, in euro cents. Minimum 200000 (€2,000). Indicative only: the price is set in the commercial proposal.
target_categoriesNoCreator categories whose audience fits the product.

Output Schema

ParametersJSON Schema
NameRequiredDescription
emailedNotrue when the claim link was also sent to the email you passed.
draft_idNo
claim_urlNoPublic URL to give to the user. No login needed to view it.
next_stepNoWhat to tell the user now.
expires_atNo

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, but the description adds the behavior that actually matters: nothing is charged, nothing reaches creators before proposal acceptance, the draft expires in 7 days, and the tool must not promise views/videos/creators. This is exactly the kind of context structured fields cannot convey.

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?

Front-loaded with the routing instruction and the key no-account constraint, and most sentences carry distinct operational information. It is on the long side, but the length is justified by the amount of non-obvious behavior it discloses.

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 no explanation, yet the description still calls out claim_url as the deliverable. Combined with the workflow, expiration, billing, and no-promise constraints, an agent has everything needed to invoke this correctly and set user expectations.

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 already 80%, so the schema carries most parameter meaning. The description still adds value beyond it: the consequence of passing email (the user also receives the link), that budget_max_cents is indicative with a €2,000 floor, and instruction to populate company from the user's website.

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 opens with a specific verb+resource ("Builds a campaign draft") and an explicit scope ("WITHOUT any account or API key"), then states the concrete artifact returned (claim_url). It is trivially distinguishable from the only sibling, get_service_info.

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?

"START HERE when a user asks how to promote their app, software, service, game or course, or wants UGC videos" is an explicit trigger condition, and the description explains the downstream flow (claim link, 6-digit code, proposal). It does not, however, state any when-not condition or name an alternative tool to prefer in other situations.

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

get_service_infoGet service infoA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
mcpNo
docsNo
nameNo
toolsNo
pausedNo
contactNo
openapiNo
pricingNoThe price model, to relay as is.
currencyNo
platformsNo
categoriesNo
budget_unitNo
descriptionNo
order_modelNo
how_it_worksNoWhat happens after a draft, to tell the user.
max_campaign_budget_centsNo
min_campaign_budget_centsNo

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcreate_campaign_draft1 field changed
      • changedInput schema / properties / budget_max_cents / description
        Previous value: -"The flat campaign package the user has in mind, in euro cents. Minimum 200000 (€2,000). Indicative: the final price is in the commercial proposal. Not a spend cap, not pay-per-video."New value: +"The budget the user has in mind for the campaign, in euro cents. Minimum 200000 (€2,000). Indicative only: the price is set in the commercial proposal."
  2. 8 tool updates
    • Removedcheck_campaign_status
    • Changedcreate_campaign_draft18 fields changed
      • addedInput schema / properties / brief / description
        Added value: +"What the product is, who it is for, and what the videos should show."
      • changedInput schema / properties / budget_max_cents / description
        Previous value: -"Campaign package, in euro cents. Minimum 200000 (€2,000), invoiced in full."New value: +"The flat campaign package the user has in mind, in euro cents. Minimum 200000 (€2,000). Indicative: the final price is in the commercial proposal. Not a spend cap, not pay-per-video."
      • changedInput schema / properties / company / description
        Previous value: -"The company the campaign is for, as you understood it. Shown on the claim page and pre-fills their profile."New value: +"The company the campaign is for, as you understood it. Shown on the claim page."
      • removedInput schema / properties / cpm_cents
        Removed value: -{
-  "description": "Variable pay per 1,000 views, in euro cents. Defaults to 100 (€1). There is NO flat-fee field: the flat fee is computed from the measured quality and reach of each creator’s accounts, and is paid once per challenge however many videos they post.",
-  "maximum": 5000,
-  "minimum": 0,
-  "type": "integer"
-}
      • addedInput schema / properties / deadline / description
        Added value: +"YYYY-MM-DD, in the future. Any other value is ignored."
      • changedInput schema / properties / email / description
        Previous value: -"The user's email, if they gave it. Lets them receive the campaign by mail instead of only through this chat."New value: +"The user's email, if they gave it. They receive the claim link by email too."
      • addedInput schema / properties / language
        Added value: +{
+  "description": "The user's language, for that email. Defaults to the language of the brief.",
+  "enum": [
+    "fr",
+    "en"
+  ],
+  "type": "string"
+}
      • removedInput schema / properties / max_cents
        Removed value: -{
-  "description": "Maximum payout per creator, in euro cents. Defaults to 50000 (€500).",
-  "maximum": 200000,
-  "minimum": 1,
-  "type": "integer"
-}
      • removedInput schema / properties / min_cents
        Removed value: -{
-  "description": "Minimum payout per creator once the views threshold is cleared, in euro cents.",
-  "maximum": 200000,
-  "minimum": 0,
-  "type": "integer"
-}
      • removedInput schema / properties / min_views
        Removed value: -{
-  "description": "Views needed to unlock payment, counted CUMULATIVELY across all videos a creator posts for this campaign, not per video: three videos at 400 views clear a threshold of 1000. Below it nothing is payable.",
-  "minimum": 0,
-  "type": "integer"
-}
      • addedInput schema / properties / objectives / maxItems
        Added value: +6
      • removedInput schema / properties / payment_trigger
        Removed value: -{
-  "enum": [
-    "publication",
-    "views"
-  ],
-  "type": "string"
-}
      • removedInput schema / properties / prestation
        Removed value: -{
-  "enum": [
-    "video_post"
-  ],
-  "type": "string"
-}
      • addedInput schema / properties / target_categories / description
        Added value: +"Creator categories whose audience fits the product."
      • addedInput schema / properties / title / description
        Added value: +"Campaign title, e.g. the product and the angle."
      • removedInput schema / properties / views_threshold
        Removed value: -{
-  "minimum": 0,
-  "type": "integer"
-}
      • addedOutput schema / properties / emailed
        Added value: +{
+  "description": "true when the claim link was also sent to the email you passed.",
+  "type": "boolean"
+}
      • addedOutput schema / properties / next_step / description
        Added value: +"What to tell the user now."
    • Removedcreate_campaign_order
    • Removedestimate_campaign
    • Changedget_service_info8 fields changed
      • 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"
+}
    • Removedlist_my_campaigns
    • Removedlist_my_deliverables
    • Removedsubmit_posted_video
  3. 2 tool updates
    • Changedcreate_campaign_draft1 field changed
      • changedInput schema / properties / prestation / enum
        Previous value: -[
-  "ugc_only",
-  "video_post",
-  "post_provided"
-]New value: +[
+  "video_post"
+]
    • Changedcreate_campaign_order1 field changed
      • changedInput schema / properties / prestation / enum
        Previous value: -[
-  "ugc_only",
-  "video_post",
-  "post_provided"
-]New value: +[
+  "video_post"
+]
  4. 2 tool updates
    • Changedcreate_campaign_draft1 field changed
      • changedInput schema / properties / budget_max_cents / description
        Previous value: -"Spend cap for the whole campaign, in euro cents. Minimum 200000 (€2,000)."New value: +"Campaign package, in euro cents. Minimum 200000 (€2,000), invoiced in full."
    • Changedcreate_campaign_order1 field changed
      • changedInput schema / properties / budget_max_cents / description
        Previous value: -"Maximum spend for the whole campaign, in euro cents. Minimum 200000 (€2,000), maximum 10000000 (€100,000). This is a cap: unspent budget is never charged."New value: +"Campaign package, in euro cents. Minimum 200000 (€2,000), maximum 10000000 (€100,000). Invoiced in full: it is not a spend cap and not consumable credit."
  5. 1 tool update
    • Changedestimate_campaign1 field changed
      • removedOutput schema / properties / estimate
        Removed value: -{
-  "description": "What the suggested cap can produce: budget_max_cents, estimated_creators, estimated_videos (5 per creator), max_views (at €1 per 1,000 views). Null if no budget can be inferred. The cap is not an invoice: unspent budget is never charged.",
-  "type": [
-    "object",
-    "null"
-  ]
-}
  6. 2 tool updates
    • Changedcreate_campaign_draft4 fields changed
      • addedInput schema / properties / cpm_cents
        Added value: +{
+  "description": "Variable pay per 1,000 views, in euro cents. Defaults to 100 (€1). There is NO flat-fee field: the flat fee is computed from the measured quality and reach of each creator’s accounts, and is paid once per challenge however many videos they post.",
+  "maximum": 5000,
+  "minimum": 0,
+  "type": "integer"
+}
      • addedInput schema / properties / max_cents
        Added value: +{
+  "description": "Maximum payout per creator, in euro cents. Defaults to 50000 (€500).",
+  "maximum": 200000,
+  "minimum": 1,
+  "type": "integer"
+}
      • addedInput schema / properties / min_cents
        Added value: +{
+  "description": "Minimum payout per creator once the views threshold is cleared, in euro cents.",
+  "maximum": 200000,
+  "minimum": 0,
+  "type": "integer"
+}
      • addedInput schema / properties / min_views
        Added value: +{
+  "description": "Views needed to unlock payment, counted CUMULATIVELY across all videos a creator posts for this campaign, not per video: three videos at 400 views clear a threshold of 1000. Below it nothing is payable.",
+  "minimum": 0,
+  "type": "integer"
+}
    • Changedcreate_campaign_order4 fields changed
      • addedInput schema / properties / cpm_cents
        Added value: +{
+  "description": "Variable pay per 1,000 views, in euro cents. Defaults to 100 (€1). There is NO flat-fee field: the flat fee is computed from the measured quality and reach of each creator’s accounts, and is paid once per challenge however many videos they post.",
+  "maximum": 5000,
+  "minimum": 0,
+  "type": "integer"
+}
      • addedInput schema / properties / max_cents
        Added value: +{
+  "description": "Maximum payout per creator, in euro cents. Defaults to 50000 (€500).",
+  "maximum": 200000,
+  "minimum": 1,
+  "type": "integer"
+}
      • addedInput schema / properties / min_cents
        Added value: +{
+  "description": "Minimum payout per creator once the views threshold is cleared, in euro cents.",
+  "maximum": 200000,
+  "minimum": 0,
+  "type": "integer"
+}
      • addedInput schema / properties / min_views
        Added value: +{
+  "description": "Views needed to unlock payment, counted CUMULATIVELY across all videos a creator posts for this campaign, not per video: three videos at 400 views clear a threshold of 1000. Below it nothing is payable.",
+  "minimum": 0,
+  "type": "integer"
+}
  7. 2 tool updates
    • Changedcreate_campaign_draft3 fields changed
      • changedInput schema / properties / budget_max_cents / description
        Previous value: -"Spend cap for the whole campaign, in euro cents. Minimum 300000 (€3,000)."New value: +"Spend cap for the whole campaign, in euro cents. Minimum 200000 (€2,000)."
      • changedInput schema / properties / budget_max_cents / minimum
        Previous value: -300000New value: +200000
      • changedInput schema / properties / platforms / items / enum
        Previous value: -[
-  "TikTok",
-  "Instagram",
-  "YouTube",
-  "Snapchat",
-  "Facebook"
-]New value: +[
+  "TikTok",
+  "Instagram"
+]
    • Changedcreate_campaign_order3 fields changed
      • changedInput schema / properties / budget_max_cents / description
        Previous value: -"Maximum spend for the whole campaign, in euro cents. Minimum 300000 (€3,000), maximum 10000000 (€100,000). This is a cap: unspent budget is never charged."New value: +"Maximum spend for the whole campaign, in euro cents. Minimum 200000 (€2,000), maximum 10000000 (€100,000). This is a cap: unspent budget is never charged."
      • changedInput schema / properties / budget_max_cents / minimum
        Previous value: -300000New value: +200000
      • changedInput schema / properties / platforms / items / enum
        Previous value: -[
-  "TikTok",
-  "Instagram",
-  "YouTube",
-  "Snapchat",
-  "Facebook"
-]New value: +[
+  "TikTok",
+  "Instagram"
+]
  8. 1 tool update
    • Addedcreate_campaign_draft
  9. 1 tool update
    • Changedget_service_info2 fields changed
      • 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"
+}
  10. 4 tool updates
    • Changedcreate_campaign_order4 fields changed
      • addedInput schema / properties / budget_max_cents
        Added value: +{
+  "description": "Maximum spend for the whole campaign, in euro cents. Minimum 300000 (€3,000), maximum 10000000 (€100,000). This is a cap: unspent budget is never charged.",
+  "maximum": 10000000,
+  "minimum": 300000,
+  "type": "integer"
+}
      • removedInput schema / properties / budget_per_creator_cents
        Removed value: -{
-  "maximum": 200000,
-  "minimum": 5000,
-  "type": "integer"
-}
      • removedInput schema / properties / creators_wanted
        Removed value: -{
-  "maximum": 50,
-  "minimum": 1,
-  "type": "integer"
-}
      • changedInput schema / required
        Previous value: -[
-  "title",
-  "brief",
-  "budget_per_creator_cents",
-  "creators_wanted"
-]New value: +[
+  "title",
+  "brief",
+  "budget_max_cents"
+]
    • Changedestimate_campaign3 fields changed
      • addedOutput schema / properties / estimate
        Added value: +{
+  "description": "What the suggested cap can produce: budget_max_cents, estimated_creators, estimated_videos (5 per creator), max_views (at €1 per 1,000 views). Null if no budget can be inferred. The cap is not an invoice: unspent budget is never charged.",
+  "type": [
+    "object",
+    "null"
+  ]
+}
      • removedOutput schema / properties / indicative_total_cents
        Removed value: -{
-  "type": [
-    "integer",
-    "null"
-  ]
-}
      • changedOutput schema / properties / suggested / description
        Previous value: -"Structured campaign fields inferred from the brief."New value: +"Structured campaign fields inferred from the brief (including budget_max_cents)."
    • Changedget_service_info2 fields changed
      • removedOutput schema / properties / min_budget_per_creator_cents
        Removed value: -{
-  "type": "integer"
-}
      • addedOutput schema / properties / min_campaign_budget_cents
        Added value: +{
+  "type": "integer"
+}
    • Changedlist_my_campaigns2 fields changed
      • removedOutput schema / properties / campaigns / items / properties / budget_per_creator_cents
        Removed value: -{
-  "type": [
-    "integer",
-    "null"
-  ]
-}
      • addedOutput schema / properties / campaigns / items / properties / remuneration
        Added value: +{
+  "description": "Fixed fee set by an internal method scoring the quality of your accounts, plus €1 per 1000 views capped at €500 per creator.",
+  "type": "string"
+}
  11. 1 tool update
    • Changedcreate_campaign_order1 field changed
      • changedInput schema / properties / target_categories / items / enum
        Previous value: -[
-  "dog",
-  "cat",
-  "car",
-  "cooking",
-  "couple",
-  "business",
-  "podcast",
-  "sport"
-]New value: +[
+  "dog",
+  "cat",
+  "car",
+  "cooking",
+  "couple",
+  "business",
+  "podcast",
+  "sport",
+  "beauty",
+  "fashion",
+  "tech",
+  "home",
+  "travel",
+  "wellness",
+  "family",
+  "gaming",
+  "finance",
+  "diy",
+  "garden",
+  "pets",
+  "lifestyle",
+  "kids"
+]
  12. 3 tool updates
    • Addedlist_my_campaigns
    • Addedlist_my_deliverables
    • Addedsubmit_posted_video
  13. 4 tool updates
    • First observedcheck_campaign_status
    • First observedcreate_campaign_order
    • First observedestimate_campaign
    • First observedget_service_info

Related MCP Connectors

Related MCP Servers

  • Prizmad by prizmad

    Prizmadofficial

    prizmad
    A
    license
    Not graded
    quality
    D
    maintenance
    Generate AI UGC video ads from any product URL in 5 minutes. Realistic AI avatars, natural voiceover, proven ad templates. No actors, no editing, no experience required.
    40 npm
    1
    MIT

  • Clipwright

    seocombat
    A
    license
    A
    quality
    A
    maintenance
    Make UGC-style video ads without filming: tell your AI assistant what to say and get a vertical clip of a realistic actor saying it, ready for TikTok, Reels or Shorts. Pick or describe an actor, choose a voice from samples, and see the price before rendering. It also makes faceless videos from a script or a short brief: narration over an opening animated clip and image scenes.
    17
    1
    MIT
  • clipugc by clipugc

    clipugcofficial

    clipugc
    A
    license
    A
    quality
    A
    maintenance
    Make UGC videos for mobile apps with AI influencers who keep the same face, from any MCP client. Create a character, generate new looks, turn a look into a 5 or 10 second clip, add your app screen recording and a hook, then download the finished vertical video. Needs a ClipUGC API key.
    12
    682 npm
    2
    MIT
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