Skip to main content
Glama

Account & History

manage_account
Destructive

Review Slideforge balance, usage, job history, and feedback; top up credits, manage webhooks, or delete jobs and assets.

Instructions

SlideForge account for PowerPoint generation: balance, billing, job history, feedback, data controls. All free. Actions: status (balance+plan), usage (spend breakdown), jobs (history), job (single job detail — slide jobs include quality_warnings[]; deck jobs add slides_completed/slides_failed/failed_slides[]), feedback (submit), feedback_list (read your reports back: status + resolution), onboarding (capabilities overview), topup (Stripe checkout link; wallet credits automatically), webhooks/webhook_add/webhook_remove/webhook_test (push endpoint instead of polling to terminal), download_url (fresh short-TTL PPTX link for an owned job — when a result carries no inline URL), security_status (retention + access-model + deletion posture), delete_job (irreversible: job + versions + files) Action delete_asset irreversibly deletes a user-owned uploaded/generated image asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoHTTPS endpoint to receive events (for action=webhook_add). Must be public HTTPS (private/loopback rejected).
daysNoLookback period (for action=usage, default 30)
slugNoReport slug (for action=reports — returns one report's full metadata; omit to list all).
limitNoMax rows (action=jobs default 10; action=feedback_list default 50, max 100)
actionYesOperation (required). feedback → report a defect or request against a render; pass job_id so it is actionable, and ask the user before filing. feedback_list → read YOUR OWN filed reports back, with `status` and the `resolution` written when one was acted on: check it before working around a defect you reported earlier, because it may already be fixed. brand_report → the per-token fidelity report for one of your brand kits (pass theme_id). topup → mints a Stripe checkout link the user pays at directly (wallet credits automatically) — use when a render is refused for balance. reports → list report types; webhook_add registers a push endpoint instead of polling — see the url/events props. delete_job is irreversible. delete_asset is irreversible for user-owned image assets.
amountNoUSD top-up amount (for action=topup, default 10, min 10, max 1000). Volume bonus: $50→+10%, $100→+15%, $200→+20%.
detailNoFor action=status only: default false masks identity fields; true returns full email/user_id diagnostics for the authenticated user.
eventsNoEvent types to subscribe to (for action=webhook_add; default all): job.completed, job.failed, deck.completed, deck.partial, deck.failed.
job_idNoJob ID (for action=job, action=download_url and action=delete_job)
statusNoFilter — action=jobs: queued/generating/complete/failed; action=feedback_list: open/resolved
messageNoWhat went wrong or what you want, in the user's own words (for action=feedback).
asset_idNoImage asset ID (for action=delete_asset). Logos are content-addressed/shared and are not deleted by this action.
categoryNoFeedback category (action=feedback to file under it, action=feedback_list to filter by it). The first nine are slide-quality categories — pair them with job_id.
severityNoFor action=feedback: `bug` = it is broken, `quality` = it rendered but reads poorly, `suggestion` = a request. Defaults to suggestion, so file real defects explicitly or they are triaged as wishes.
webhook_idNoWebhook subscription id (for action=webhook_remove / webhook_test).
include_previewNoPreview (for action=job)
include_childrenNoFor action=jobs: include deck child slides (each carries parent_deck_id) so a deck's slides are discoverable by listing. Default false (parents only). Deck rows roll child cost up to the deck.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv5.9.0
    • changedInput schema / properties / action / description
      Previous value: -"Operation (required). reports → list report types; webhook_add registers a push endpoint instead of polling — see the url/events props. delete_job is irreversible. delete_asset is irreversible for user-owned image assets."New value: +"Operation (required). feedback → report a defect or request against a render; pass job_id so it is actionable, and ask the user before filing. feedback_list → read YOUR OWN filed reports back, with `status` and the `resolution` written when one was acted on: check it before working around a defect you reported earlier, because it may already be fixed. brand_report → the per-token fidelity report for one of your brand kits (pass theme_id). topup → mints a Stripe checkout link the user pays at directly (wallet credits automatically) — use when a render is refused for balance. reports → list report types; webhook_add registers a push endpoint instead of polling — see the url/events props. delete_job is irreversible. delete_asset is irreversible for user-owned image assets."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "status",
      -  "usage",
      -  "jobs",
      -  "job",
      -  "download_url",
      -  "feedback",
      -  "onboarding",
      -  "reports",
      -  "webhooks",
      -  "webhook_add",
      -  "webhook_remove",
      -  "webhook_test",
      -  "security_status",
      -  "delete_job",
      -  "delete_asset"
      -]New value: +[
      +  "status",
      +  "usage",
      +  "jobs",
      +  "job",
      +  "download_url",
      +  "feedback",
      +  "feedback_list",
      +  "onboarding",
      +  "topup",
      +  "brand_report",
      +  "reports",
      +  "webhooks",
      +  "webhook_add",
      +  "webhook_remove",
      +  "webhook_test",
      +  "security_status",
      +  "delete_job",
      +  "delete_asset"
      +]
    • addedInput schema / properties / amount
      Added value: +{
      +  "description": "USD top-up amount (for action=topup, default 10, min 10, max 1000). Volume bonus: $50→+10%, $100→+15%, $200→+20%.",
      +  "type": "number"
      +}
    • changedInput schema / properties / category / description
      Previous value: -"Feedback category (for action=feedback): bug/feature_request/quality/general"New value: +"Feedback category (action=feedback to file under it, action=feedback_list to filter by it). The first nine are slide-quality categories — pair them with job_id."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "layout",
      +  "typography",
      +  "contrast",
      +  "content",
      +  "icons",
      +  "images",
      +  "theme",
      +  "chrome",
      +  "consistency",
      +  "bug",
      +  "feature_request",
      +  "testimonial",
      +  "general",
      +  "other"
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Max jobs (for action=jobs, default 10)"New value: +"Max rows (action=jobs default 10; action=feedback_list default 50, max 100)"
    • changedInput schema / properties / message / description
      Previous value: -"Feedback text (for action=feedback)"New value: +"What went wrong or what you want, in the user's own words (for action=feedback)."
    • addedInput schema / properties / severity
      Added value: +{
      +  "description": "For action=feedback: `bug` = it is broken, `quality` = it rendered but reads poorly, `suggestion` = a request. Defaults to suggestion, so file real defects explicitly or they are triaged as wishes.",
      +  "enum": [
      +    "bug",
      +    "quality",
      +    "suggestion"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / status / description
      Previous value: -"Filter (for action=jobs): queued/generating/complete/failed"New value: +"Filter — action=jobs: queued/generating/complete/failed; action=feedback_list: open/resolved"
  2. First observedv5.5.4

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing irreversibility of delete_job and delete_asset, automatic wallet credit on topup, volume bonuses, the fact that logos are content-addressed/shared and not deleted, and the severity default to 'suggestion'. These are genuinely useful behavioral details.

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 dense but front-loaded with an action inventory before detailed explanations. Given 18 actions and 17 parameters, the length is largely justified. There is some redundancy where the action parameter description repeats parts of the initial inventory, but it remains scannable.

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?

The description covers most actions and destructive semantics thoroughly, but the missing theme_id parameter for brand_report and the conflicting reports action description are real invocation hazards. Several actions such as onboarding, webhook_test, and security_status lack expected behavior or return detail, and with no output schema the description must carry more weight than it does.

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 100%, so the baseline is 3, but the description adds meaningful semantics: amount volume bonuses, detail masking identity fields, include_children cost roll-up, and severity defaulting. However, it loses a point because action=brand_report tells the agent to pass theme_id, yet theme_id is not present in the schema, and reports behavior is described inconsistently between the action summary and the slug parameter.

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 opening sentence names the exact domain ('SlideForge account for PowerPoint generation: balance, billing, job history, feedback, data controls') and the action list enumerates the operations in detail. This clearly differentiates the tool from sibling tools like create_slide, create_deck, and upload_asset.

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?

The description gives explicit selection guidance: use topup when a render is refused for balance, use webhooks instead of polling, use download_url when a result carries no inline URL, and check feedback_list before working around a previously reported defect. It also instructs the agent to ask the user before filing feedback.

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

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/smartdatabrokers/slideforge-mcp'

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