Glide
Read and write rows in Glide Big Tables, manage table schema, and stage large datasets with stashing over the Glide API.
About
Glide ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.glide- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Databases · Developer Tools · Productivity
Overview
Glide is a no-code app builder, and this app covers the one thing its public API actually exposes: Big Tables — Glide’s large-capacity cloud data type — over the classic Glide API at api.glideapps.com.
That surface is table row CRUD (list, get, add, update, delete), table lifecycle (create and overwrite, with schema inference or an explicit column schema), version-aware writes via ETag/If-Match to avoid clobbering concurrent edits, stashing for datasets too large to send inline (up to 15 MB per request), asynchronous job polling for table writes that Glide defers, and the file-upload handshake that hands back a public URL for a Glide app.
Glide’s API is deliberately narrow: it only ever sees Big Tables, never the spreadsheet-backed tables most Glide apps are built on, and every write it can make is bounded by the same schema-conformance rules the Data Editor enforces. Nothing here reaches into app configuration, layouts, users, or billing — none of that is exposed by the vendor.
Build with Glide
Three routes to the same 14 actions. The Workflow tab is generated from Glide's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Job Status
job-status-get Check the status of an asynchronous table job: running, succeeded, or failed.
Get Rows Version
rows-version-get Read a Big Table's current version (ETag) without fetching its rows.
Stash Data
stash-data Upload one chunk of a large dataset to a stash, for use by Create/Overwrite Table or Add Rows to Table.
Create Table
table-create Create a new Big Table, optionally with an explicit column schema and initial rows.
List Tables
table-list List every Big Table this connection's team owns. Only Big Tables are returned.
Overwrite Table
table-overwrite Clear every row in a Big Table and optionally replace them, and/or its schema.
Create Upload
upload-create Start a file upload and get a pre-signed URL to PUT the file's bytes to. Does not itself upload the bytes — see the action's description for why.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Glide's real ids.
{
"manifestVersion": "2",
"name": "glide-example",
"steps": [
{
"id": "job-status-get",
"uses": {
"app": "io.w6w.glide",
"action": "job-status-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"jobId": "<jobId>"
}
}
]
}Here are some of the things you can do
-
Get Job Status
readjob-status-get -
Get Row by ID
readrow-get -
Update Row
performrow-update -
Add Rows to Table
performrows-add -
Get Rows
searchrows-list
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Glide, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Glide. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "job-status-get",
payload: {
jobId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action job-status-get --payload '{"jobId":"<value>"}'Give an AI agent Glide — without giving it Glide's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.glide#job-status-get",
"input": {
"jobId": "<jobId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Glide connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Glide's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Glide itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Glide declares its own checks, so its health is a property of the app rather than something the host guesses at.
Glide platform status
Reads status.glideapps.com's Atom incident-history feed for open incidents.