shiply

Insert a record into a collection

data_insert

Insert one record into a collection. Goes through the same public visitor endpoint a browser would use — manifest access.insert decides whether it is allowed. Use to seed waitlist data, test forms end-to-end, etc.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	owned site slug
`record`	Yes	the record fields to insert as key/value pairs
`collection`	Yes	collection name to insert into

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJun 23, 2026

addedInput schema / properties / collection / description
```
Added value: +"collection name to insert into"
```

addedInput schema / properties / record / description

Added value: +"the record fields to insert as key/value pairs"

addedInput schema / properties / slug / description
```
Added value: +"owned site slug"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedJun 23, 2026

TDQS

A4/5.0

Behavior3/5

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

The description adds behavioral context by noting the endpoint is a public visitor endpoint and that 'manifest access.insert' determines permission. However, it does not discuss idempotency (annotations already note idempotentHint=false) or error handling. Overall, it provides some value beyond annotations.

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?

The description is highly concise at two sentences. The first sentence defines the core function, and the second provides context and use cases. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 params, nested object, output schema), the description is fairly complete. It covers purpose, endpoint, and use cases. While it omits details like return format, the presence of an output schema mitigates this. Some minor gaps remain (e.g., behavior on duplicate), but overall reasonable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond what the schema already provides for parameters (slug, collection, record). It mentions 'record' but without extra detail.

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 clearly states the tool's purpose: 'Insert one record into a collection.' It uses a specific verb ('Insert') and resource ('record'), and includes example use cases ('seed waitlist data, test forms end-to-end'), effectively distinguishing it from sibling tools like data_export_collection and data_query.

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?

The description provides explicit usage context ('Use to seed waitlist data, test forms end-to-end') and implies when to use this tool (for inserts). It does not explicitly state when not to use it, but the sibling tools cover reads and exports, making the guidelines adequate.

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

All shiply tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?