Senja MCP Server

Import a testimonial

create_testimonial

Destructive

Generates one text or video testimonial from an authorized customer statement, requiring explicit approval before publishing.

Instructions

Create one text/video testimonial from an authorized existing customer statement. Explicit approval is required.

Input Schema

Name	Required	Description
`url`	No	HTTPS URL without embedded credentials; provider retrieves media where supported.
`date`	No
`tags`	No
`text`	No
`type`	No
`media`	No
`title`	No
`rating`	No
`account`	No	Exact configured private account profile label; not a tenant or provider account ID.
`confirm`	No	Set true only when the user asked for exactly this action.
`form_id`	No
`payload`	No	Complete native JSON body; do not mix with body flags or payload_file. Arrays use repeated JSON object flags or a whole native array in a private file.
`approved`	No	Explicitly true publishes the testimonial; false keeps it pending.
`video_url`	No	HTTPS URL without embedded credentials; provider retrieves media where supported.
`integration`	No
`customer_url`	No	HTTPS URL without embedded credentials; provider retrieves media where supported.
`payload_file`	No	Absolute regular non-symlink JSON body file, at most 1 MiB. Cannot mix with payload/body flags.
`customer_name`	No
`thumbnail_url`	No	HTTPS URL without embedded credentials; provider retrieves media where supported.
`customer_email`	No
`customer_avatar`	No	HTTPS URL without embedded credentials; provider retrieves media where supported.
`customer_company`	No
`customer_tagline`	No
`customer_username`	No
`customer_company_logo`	No	HTTPS URL without embedded credentials; provider retrieves media where supported.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv3.0.0Oct 6, 2026

addedInput schema / $defs

Added value: +{
+  "integration": {
+    "enum": [
+      "twitter",
+      "product_hunt",
+      "google",
+      "facebook",
+      "reddit",
+      "capterra",
+      "g2",
+      "linkedin",
+      "app_store",
+      "trustpilot",
+      "shopify",
+      "play_store",
+      "yelp",
+      "slack",
+      "discord",
+      "apple_podcasts",
+      "telegram",
+      "whatsapp",
+      "instagram",
+      "youtube",
+      "tiktok",
+      "appsumo",
+      "amazon",
+      "zillow",
+      "udemy",
+      "chrome_web_store",
+      "airbnb",
+      "skillshare",
+      "realtor",
+      "sourceforge",
+      "whop",
+      "wordpress",
+      "fiverr",
+      "homestars",
+      "web_page"
+    ],
+    "type": "string"
+  },
+  "media": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "alt": {
+          "description": "",
+          "minLength": 1,
+          "type": "string"
+        },
+        "type": {
+          "enum": [
+            "image",
+            "video"
+          ],
+          "type": "string"
+        },
+        "url": {
+          "description": "",
+          "format": "uri",
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "type"
+      ],
+      "type": "object"
+    },
+    "maxItems": 100,
+    "type": "array"
+  }
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for the requested mutation or exclusive private output file."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / integration / $ref
```
Added value: +"#/$defs/integration"
```

removedInput schema / properties / integration / enum

Removed value: -[
-  "twitter",
-  "product_hunt",
-  "google",
-  "facebook",
-  "reddit",
-  "capterra",
-  "g2",
-  "linkedin",
-  "app_store",
-  "trustpilot",
-  "shopify",
-  "play_store",
-  "yelp",
-  "slack",
-  "discord",
-  "apple_podcasts",
-  "telegram",
-  "whatsapp",
-  "instagram",
-  "youtube",
-  "tiktok",
-  "appsumo",
-  "amazon",
-  "zillow",
-  "udemy",
-  "chrome_web_store",
-  "airbnb",
-  "skillshare",
-  "realtor",
-  "sourceforge",
-  "whop",
-  "wordpress",
-  "fiverr",
-  "homestars",
-  "web_page"
-]

removedInput schema / properties / integration / type
```
Removed value: -"string"
```
addedInput schema / properties / media / $ref
```
Added value: +"#/$defs/media"
```

removedInput schema / properties / media / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "alt": {
-      "description": "",
-      "minLength": 1,
-      "type": "string"
-    },
-    "type": {
-      "enum": [
-        "image",
-        "video"
-      ],
-      "type": "string"
-    },
-    "url": {
-      "description": "",
-      "format": "uri",
-      "minLength": 1,
-      "type": "string"
-    }
-  },
-  "required": [
-    "url",
-    "type"
-  ],
-  "type": "object"
-}

removedInput schema / properties / media / maxItems
```
Removed value: -100
```
removedInput schema / properties / media / type
```
Removed value: -"array"
```
addedInput schema / properties / payload / properties / integration / $ref
```
Added value: +"#/$defs/integration"
```

removedInput schema / properties / payload / properties / integration / enum

Removed value: -[
-  "twitter",
-  "product_hunt",
-  "google",
-  "facebook",
-  "reddit",
-  "capterra",
-  "g2",
-  "linkedin",
-  "app_store",
-  "trustpilot",
-  "shopify",
-  "play_store",
-  "yelp",
-  "slack",
-  "discord",
-  "apple_podcasts",
-  "telegram",
-  "whatsapp",
-  "instagram",
-  "youtube",
-  "tiktok",
-  "appsumo",
-  "amazon",
-  "zillow",
-  "udemy",
-  "chrome_web_store",
-  "airbnb",
-  "skillshare",
-  "realtor",
-  "sourceforge",
-  "whop",
-  "wordpress",
-  "fiverr",
-  "homestars",
-  "web_page"
-]

removedInput schema / properties / payload / properties / integration / type
```
Removed value: -"string"
```
addedInput schema / properties / payload / properties / media / $ref
```
Added value: +"#/$defs/media"
```

removedInput schema / properties / payload / properties / media / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "alt": {
-      "description": "",
-      "minLength": 1,
-      "type": "string"
-    },
-    "type": {
-      "enum": [
-        "image",
-        "video"
-      ],
-      "type": "string"
-    },
-    "url": {
-      "description": "",
-      "format": "uri",
-      "minLength": 1,
-      "type": "string"
-    }
-  },
-  "required": [
-    "url",
-    "type"
-  ],
-  "type": "object"
-}

removedInput schema / properties / payload / properties / media / maxItems
```
Removed value: -100
```
removedInput schema / properties / payload / properties / media / type
```
Removed value: -"array"
```

First observedv2.0.0Oct 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds only 'explicit approval is required', without explaining that the operation is non-idempotent (repeated calls may duplicate), what gets destroyed/altered, or how the confirm/approved booleans interact. For a destructive, non-idempotent create with 25 parameters, this is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action front-loaded and no filler. It is efficient, though it errs toward under-specification given the tool's complexity rather than genuine conciseness.

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

Completeness2/5

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

With 25 parameters, nested objects, no output schema, and a destructive non-idempotent profile, the description should carry far more context than two sentences. Key behaviors (payload exclusivity, publish vs pending via approved, confirm semantics) live only in schema fragments and are never surfaced coherently.

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

Parameters2/5

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

Schema description coverage is only 44% across 25 parameters, including a nested payload object, media arrays, an integration enum, and the semantically loaded confirm/approved flags. The description mentions only that the testimonial is text or video, adding essentially nothing about the payload-vs-flat-parameter relationship, payload_file exclusivity, or the approval flag's effect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Create one text/video testimonial') and scopes the source ('from an authorized existing customer statement'), which distinguishes it from list/get/update/delete siblings. It does not, however, differentiate itself from the batch-submission sibling (submit_testimonial_batch), which has an overlapping purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Explicit approval is required' implies a gate on invocation, but the description never says when to prefer this single-create tool over submit_testimonial_batch or preview_testimonial_batch, nor does it reference the confirm flag that the schema itself describes. Usage is only implied.

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

Deploy Server

Import a testimonial

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools