acknowledge_feedback_responses
ChatGPTAcknowledge feedback responses after the agent has processed them. Use this to stop processed responses from appearing in advisories and list_feedback_responses. Acknowledgement is durable and idempotent.
By Charming
Charming is a secure cloud for apps you build with Claude. Ask Claude to build an app with Charming. Charming gives your app a link you can open anywhere and use to invite people to use it with you. It’s free to use.
search_templates result, or a Template shared with them); a Template copy records its source. The copy is owned by the user and private: it keeps the source code, styles, icon, and network settings, never sharing, Public or Template state, secrets, Routines, Webhooks, domains, or version history. It never replaces an app: without manifest_id the copy takes the next free manifest id (<id>-2, <id>-3), and a manifest_id you already hold fails with manifest_id_conflict. The UI keeps working unchanged. Pass include_data: true to copy the stored data and assets too; only the app’s owner can, and a team app’s data stays in the team, and the data must fit the 24 MiB a copy carries and the account storage allowance. Pass an idempotency_key to make a retry safe: the same key returns the first copy instead of making another. secretsNotCopied names any secrets to set on the copy. Give the user shareUrl to open the copy; url is machine-only.module reuses a manifest.id the caller already owns, the new app replaces the existing app module, UI, and styles in place; use update_app to edit a known app ID by UUID. Apps persist state through a backend env.storage (Workers KV) binding and call backend operations from the frontend via window.charming.api. The module, ui, and description parameter docs carry the authoring rules — including the fill-viewport outer-container rule on ui; the charming:app-guide prompt has the full guide and a canonical example. Read the public docs without a browser using read_docs({ path: "build-mcp.md" }); read_docs({}) lists available pages. If a request needs in-app AI calls, external integrations, native apps, scheduled jobs, SQL, notifications, or view-only sharing, do not fake support. Build the closest local-state version, then log the gap with submit_feedback. The charming:app-guide prompt has alternatives. The charming:design-guide prompt documents Charming's default visual style for generated ui (single accent, warm neutrals, real type hierarchy; no gradients or decorative emoji) — a default that yields to any user-requested aesthetic. When telling the user where to open or share the app, always give them shareUrl from the result — never the url field, which is machine-only and embeds a write-capable access token.hourly, daily, or weekly (no cron syntax). The target op is invoked with empty input ({}), so it must not declare any required input fields. Rejects a duplicate Routine on the same (app, op) pair, and enforces a 3-per-app / 25-per-user cap.shareUrl to open or share the app; the url field is machine-only and embeds a write-capable access token.source.files, a module-contract revision returns source.module, source.ui, and source.styles. Needs permission to change the app. A revision older than the plan’s History window is refused with version_limit_exceeded.sourceSize), and the current revision for optimistic-concurrency edits. Pass that revision through update_app's expected_revision input. Use this when you need the source to inspect, debug, or edit an app the caller owns. Without bucket, the whole source comes back in source. When the source is too large for your client (check sourceSize), read one bucket at a time instead: bucket returns up to 20000 characters of whole lines in chunk; pass chunk.next_offset as offset until it is null, and pass expected_revision on each page so every page comes from one revision.live marks the revision serving visitors and restorable the ones restore_app_revision accepts. Needs permission to change the app. The list stops at the plan’s History window (historyLimit); page with before set to nextBefore.pending = invited, no access yet; accepted = active grantee; invited = email-only invite, no Charming account yet) and by role (collaborator = read + write; end-user = run + write data, not edit source; viewer = read only).[shared with you]; a read-only share also reads (view-only)). Use this to find an app's id before fetching, editing, or calling it. Returns per app: id, revision, role (owner | collaborator | end-user | viewer | team-admin | team-member), displayName, description (a search-friendly summary), url (machine API base), shareUrl (the link to give the user), lastUpdatedAt (ISO-8601 of the last write), claimed (always true for now — exposed for forward-compat), and capabilities (imports + exports). A collaborator can edit and run a shared app; an end-user can run it and write its data but cannot edit the app source; a viewer can only open and read it. The description disambiguates apps with similar display names; capabilities.exports lists each app's callable operations, exposing the cross-app integration surface without N+1 get_app_source calls. Paginate with cursor from a prior call's nextCursor line. Apps with description: null predate descriptions and have not yet been backfilled. When telling the user where to open or share an app, always give them shareUrl — never construct links for humans from the url field.app_id is set, returns rows for that one app (owner-checked); when omitted, returns rows across every app the caller owns. Paginate with cursor from a prior call's cursor field. Newest rows come first.shareUrl from the result — never the url field, which is machine-only and embeds a write-capable access token.currentRevision from list_app_revisions as expected_revision; a stale value is refused with revision_mismatch. A module-contract revision publishes at once. A package revision is rebuilt and answers with a build: poll get_app_build until it is published. Connector approvals the restored source does not declare are removed. Live app data does not change. Needs permission to change the app.https://charm.ing/<handle>/<app-name>), so changing it changes the prefix of every app URL they share. Use this to give the current user a different handle. The old handle keeps working by redirecting to the new one, so links already shared stay valid. Acts on the current signed-in user only and takes no user id. Handle rules: lowercase letters, digits, and hyphens; 3-32 chars; must start with a letter; no leading, trailing, or consecutive hyphens; some words are reserved. Rate-limited to 3 changes per rolling 30 days.message verbatim so the user understands the access granted. For write access, share with the end-user role or choose the signed-in audience setting. Template and Listed are separate settings. Idempotent: calling on an already-public app returns the same URL without re-firing analytics. Owner-only; anonymous apps must be claimed first.set_template instead. This metadata-blind alias accepts only app_id, enables Template for people who can already read the source App, and leaves listing metadata and Listed state unchanged. The original is never mutated. Use this when an older workflow requires the deprecated alias; use set_template for new work. Each copy belongs to the signed-in visitor from creation. Idempotent: calling on an already-remixable app returns the same URL without re-firing analytics. Anonymous apps cannot be made remixable; the app must be claimed first.starter_prompt: null (or an empty string) to clear and revert to the generic default. Owner-only; anonymous apps must be claimed first. Idempotent (re-setting the same value is a no-op). Length cap: 2000 characters.title, summary, content_markdown, category, cover fields, and gallery change only when supplied. Publishing with listed: true requires a nonblank resulting title and summary; every cover or gallery image needs nonblank alt text and must reference an image asset from this App. Pass listed: true to also mark it for discovery, or listed: false to unlist it. Omitting listed is a patch, not a reset: it leaves the current listed state exactly as it is (an already-listed app stays listed; a never-listed app stays unlisted), so re-affirming that an app is a template never surprises the owner by delisting it. Idempotent: calling with the same effective listed state as the current one returns the same URL without re-firing analytics. Anonymous apps cannot be made into templates; the app must be claimed first.collaborator (default) can open, edit, and run the app (shared state, same data); end-user can open the app and write its data (record entries, save state) but cannot edit the app source; viewer can only open and use the read-only surface — viewers cannot edit, run mutating ops, or change anything. If the grantee already has a share, calling this again WITH a role changes their role in place (status updated, no new invitation, no second email) — this is how you flip a collaborator to an end-user and back; re-sharing WITHOUT a role leaves the existing role untouched. No share role can ever share, delete, or transfer the app. The invitee does NOT need a Charming account first — inviting an email with no account stores a pending invitation and emails them a sign-up link; the eligible grant appears after they register and verify that email (an unknown handle still errors, since there is no address to reach). Revoke anytime with unshare_app.unset_template instead (identical effect). Stop allowing remixes of a Charming app. Use this to stop offering copies to new visitors; existing copies survive untouched. Also clears any public template listing, since a listed app must stay copyable. Idempotent: calling on an already-non-remixable app is a no-op.description so list_apps stays accurate; backfill one if an older app has none. For synchronous results, give the user shareUrl to open or share the app; the url field is machine-only and embeds a write-capable access token.interval, or enable/disable it. Re-enable is {enabled: true} — there is no separate re-enable action. Re-enabling also resets the consecutive-failure counter.{enabled: true} and resets the consecutive-failure counter. {rotate_secret: true} replaces the secret immediately and returns the new one once; the old secret stops working..js/.mjs, which needs edit access to the app), or a dataset bigger than a few KB — that would otherwise be inlined into module/ui and blow the 256 KiB source cap. Provide EXACTLY ONE of: sourceUrl (PREFERRED for any binary — the SERVER fetches the remote file, follows redirects, and the bytes never transit this tool call), text (UTF-8 dataset/JSON/CSV — no encoding needed), or dataBase64 (LAST RESORT, tiny binaries only: large base64 arguments can stall inside some MCP clients before ever reaching the server, so keep it under ~16 KB and use sourceUrl for anything bigger). The app reads the asset via window.charming.assets.getUrl(key) (for <img>/<a>/<audio>/<video>, and for import() or new Worker() of an uploaded script at the standalone app URL; chat embeds cannot run uploaded scripts) or env.assets.get(key) in its backend (the app must declare charming:storage/blob@1.0 in manifest.capabilities.imports to use env.assets). Caps: 10 MiB/asset, 50 assets/app, 100 MiB/app.Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/charming"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/charming)