What an agent can do
The tools the TileSet MCP server gives an agent, grouped by task.
An agent installs TileSet through these tools. You rarely need to name them: describe the result you want.
Set up
- setup_widget: the one to start with. Connects or reuses a source, creates or reuses a widget on it, and returns the snippet. Safe to repeat. It takes a source (
google,youtube,testimonials,pinterest,x,twitch,kick) and, for the sources that need one, a query: a Maps link, an @handle, a Pinterest profile or board link or@name(connect_sourcetakes the link aspinterestUrl), an X@handleor profile link (connect_sourcetakes it asxHandle), a Twitch channel name or twitch.tv link (connect_sourcetakes it astwitchChannel), a Kick channel name or kick.com link (connect_sourcetakes it askickChannel). Testimonials takes no query. If all you have is a link, leavesourceout:setup_widget { "query": "https://www.youtube.com/@name" }works out the platform from the address (connect_sourcedoes the same with notype). A Google Maps link goes to Google, and YouTube, Twitch, Kick, Pinterest, X links connect their own source. A link it cannot place comes back as an error asking forsource; nothing is fetched or billed to place it. For a mixed feed it takessourceIds, sources already connected, instead. - verify_install:
verify_install { "url": "<the page's URL>", "widgetId": "w_..." }fetches a public page and reports whether the script and thedivare there and whether the widget serves items. A mistake it recognizes (an invented id, a script a page builder stripped, a login or bot wall, a cached old page) comes back with a Fix line, and a missing script tag ordivcomes with the exact line to add. The dashboard’s Check my page is the same check. A page that builds itself in the browser (Lovable, React), or a Wix page, whose Embed HTML box is a frame our server cannot read, is only confirmed when thewidgetIdis given and the widget has loaded on that page once. A pass shows on the widget’s dashboard card as Installed. - get_embed_code, list_sources, connect_source, list_widgets, create_widget, update_widget, describe_widget_options.
- describe_source_content: describes what a connected source holds, as counts for choosing a design: how many items, their dates and how often new ones arrive, the star ratings, how many carry photos, videos or several pictures, picture shapes, text lengths, writing systems and owner replies. It never returns the items themselves.
- The Preview link. The widget tools answer with a Preview link,
https://app.tileset.com/preview/<widgetId>: the widget as visitors see it, to open in a browser.
What an agent never reads
An agent sets up and runs your widgets. It never reads your content: no tool returns a post or a review, its words, names, pictures or links. It chooses a layout from the counts and looks at the preview. If a source fails, the agent gets a fixed sentence, not the platform’s own answer. You see your content in the dashboard, and your visitors see it in the widget.
Link in bio
- create_bio_page: makes a Link in bio page with a name, a short bio, a picture, a look and blocks: link buttons, social icons, and blocks from the account's sources (latest posts, the newest item as a featured card, reviews). Answers the page's address to put in a profile bio. One page on the free plan. Leave
slugout and the page is given a short address of its own; choosing the slug is included with Starter and up, and the free plan gets a clear refusal naming the plan. - update_bio_page: changes any of a page's fields, including its look (
theme,modeandstyle: fonts, background, buttons, corners, picture shape and size, spacing, header, and on Starter and up your own colour and a picture background) andsearchable; a link block takes anicon(one emoji) or athumbpicture (an https link, or a JPEG sent as a data URI, which reads back asuploaded), athumbAltdescription, and a buttoncolor(a preset name such asforest, or any hex); sendblocksback in a new order to reorder them. A new address (Starter and up) keeps the old one redirecting for 30 days, an assigned one for good. add_bio_blocks adds blocks at the end, and list_bio_pages lists the pages with their addresses and every setting. delete_bio_page deletes a page, and get_bio_analytics reads its views and link clicks. None of them ever returns the content a page shows.
Testimonials
- add_testimonials: adds up to 20 testimonials to a testimonials source, each a name and the words, and if you have them a role or company, a 1 to 5 rating, a date and an https photo link. What an agent adds waits for your approval in the dashboard. It is told to add only words a real customer said, never to write testimonials itself.
- list_testimonials: counts a testimonials source’s entries: how many wait for your approval, how many are on the widget and how many the automatic check filtered as likely spam (only testimonials sent through the link are ever checked, never what an agent adds). It never returns the entries themselves. Reading, approving, declining, editing, deleting, the order and the Share a testimonial link stay in the dashboard, for a person. list_sources says when a source’s link has paused itself because its queue is full.
Update control
- update_source: rename a source (
label), set its speed or calendar schedule. A source is named after its account unlessconnect_sourceis given alabel. - update_source_now and get_update_status: Update now (Starter and up) and following a slower one.
- get_source_schedule, create_source_webhook, delete_source_webhook.
Credits
- get_credits: balance, allowance, refill date, what each speed costs, and for every live source which speeds your credits carry, which they cannot, and which are above your plan.
- set_credit_limits: the monthly cap and the account’s time zone.
Your agent never buys anything. When credits run short it tells you, and you add credits under Credits or change plan under Plans in the dashboard.
Destructive
delete_source removes a source and every widget built on it alone; a mixed widget loses the source and keeps its others. delete_widget removes a widget; pages still embedding it render nothing. Both are permanent. If you want your agent to ask first, say so in your project instructions.
For agents reading this
The authoritative, machine-readable version is llms.txt.
The server has tools only, no resources.