easysociable-mcp

Attest image rights

attest_image

Idempotent

Record immutable copyright or commercial rights ownership attestation for an image before multi-platform export. Creates permanent audit log; requires workspace owner authorization.

Instructions

Record an immutable legal copyright or commercial rights ownership attestation for an image asset. Call before multi-platform export to satisfy commercial compliance requirements. Do NOT use to edit metadata like title or tags (use update_image instead) or upload images (use import_image). Not required for personal or draft-only runs. Requires workspace owner authorization. Writes a permanent audit log record bound to imageId. Re-attesting with a new statementVersion creates a new timestamped attestation record without revoking prior history. Returns attestation confirmation object.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`imageId`	Yes	The unique image asset identifier to attest.
`statementVersion`	No	Legal attestation terms version accepted (e.g. v1). Returns 400 if invalid or empty.

Output Schema

TableJSON Schema

Name	Required	Description
`imageId`	No	Image asset ID.
`attestedAt`	No	ISO timestamp of attestation.
`statementVersion`	No	Recorded statement version.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.17Oct 5, 2026

changedInput schema / properties / statementVersion / description

Previous value: -"Legal attestation terms version accepted (e.g. v1)."New value: +"Legal attestation terms version accepted (e.g. v1). Returns 400 if invalid or empty."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attestedAt": {
+      "description": "ISO timestamp of attestation.",
+      "type": "string"
+    },
+    "imageId": {
+      "description": "Image asset ID.",
+      "type": "string"
+    },
+    "statementVersion": {
+      "description": "Recorded statement version.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedv0.1.16Oct 5, 2026
- addedInput schema / properties / imageId / description
```
Added value: +"The unique image asset identifier to attest."
```
- addedInput schema / properties / statementVersion / description
```
Added value: +"Legal attestation terms version accepted (e.g. v1)."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare the safety profile (non-read-only, idempotent, non-destructive), but the description adds substantial context beyond them: workspace owner authorization requirement, a permanent audit log record, immutability, and re-attestation semantics that preserve prior history. These are exactly the traits an agent needs before invoking a compliance write.

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?

Front-loaded with the core purpose, then usage, exclusions, authorization, and mutation semantics in order of importance. Dense but every sentence carries distinct information; nothing is padding.

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

Completeness5/5

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

An output schema exists, so return values need not be explained (the closing 'Returns attestation confirmation object' is harmless redundancy). With authorization, permanence, idempotent re-attestation behavior, and routing all covered, nothing an agent needs to call this correctly is missing.

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 baseline is 3. The description goes further by explaining statementVersion semantics — that a new version creates a new timestamped record without revoking prior history — which is meaning beyond the schema's brief field note.

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?

States a specific verb and resource ('Record an immutable legal copyright or commercial rights ownership attestation for an image asset') and explicitly distinguishes itself from siblings update_image and import_image. An agent can identify the operation and its scope without opening the schema.

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?

Gives explicit when-to-use ('Call before multi-platform export to satisfy commercial compliance requirements'), when-not-to-use with named alternatives (update_image for metadata, import_image for uploads), and an exclusion ('Not required for personal or draft-only runs'). This is close to ideal routing guidance.

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