Tulimoa

Edit one of your own Tulimoa listings

edit_listing

Update fields of a listing you own (by slug). You cannot change ownership or set review status. Any edit sends the listing back to admin review (status: pending) and it reappears publicly only after re-approval. Every listing needs a logo: pass logo_url to replace it (required if the listing has none yet). Requires a write-scoped Tulimoa login.

Input Schema

TableJSON Schema

Name	Required	Description
`mcp`	No
`url`	No
`name`	No
`slug`	Yes	Slug of YOUR listing to edit (from submit_listing).
`tags`	No
`ai_usage`	No	40 to 600 characters, ideally in English: how the software uses AI, or what agents can do with it. Be concrete, not salesy. Submissions without a clear AI or agent angle are rejected.
`category`	No
`gdpr_dpa`	No
`logo_url`	No	New logo. Public https URL of the company logo: PNG, JPEG, WebP, GIF or AVIF, at least 64 px, max 5 MB. A square icon works best. Tulimoa downloads it, scales it to max 512 px and stores it as WebP. Required if the listing has no logo yet.
`mcp_auth`	No
`x_handle`	No
`data_region`	No	Where customer data is hosted: eu (in the EU by default), eu-option (an EU region can be selected), non-eu, self-hosted (runs at the customer). Listings with EU hosting also appear on tulimoa.com/mcp-eu.
`launch_hook`	No
`mcp_docs_url`	No
`model_source`	No
`pricing_model`	No
`certifications`	No
`mcp_server_url`	No
`pricing_detail`	No
`agent_interfaces`	No
`hosting_provider`	No
`founder_x_handles`	No
`short_description`	No
`trains_on_customer_data`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Listing id.
`slug`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 3, 2026

addedInput schema / properties / agent_interfaces

Added value: +{
+  "items": {
+    "enum": [
+      "api",
+      "cli",
+      "sdk",
+      "webhooks"
+    ],
+    "type": "string"
+  },
+  "maxItems": 4,
+  "type": "array"
+}

addedInput schema / properties / ai_usage

Added value: +{
+  "description": "40 to 600 characters, ideally in English: how the software uses AI, or what agents can do with it. Be concrete, not salesy. Submissions without a clear AI or agent angle are rejected.",
+  "maxLength": 600,
+  "minLength": 40,
+  "type": "string"
+}

addedInput schema / properties / certifications

Added value: +{
+  "items": {
+    "enum": [
+      "soc2",
+      "iso27001",
+      "hipaa"
+    ],
+    "type": "string"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

addedInput schema / properties / data_region

Added value: +{
+  "description": "Where customer data is hosted: eu (in the EU by default), eu-option (an EU region can be selected), non-eu, self-hosted (runs at the customer). Listings with EU hosting also appear on tulimoa.com/mcp-eu.",
+  "enum": [
+    "eu",
+    "eu-option",
+    "non-eu",
+    "self-hosted"
+  ],
+  "type": "string"
+}

addedInput schema / properties / founder_x_handles

Added value: +{
+  "items": {
+    "maxLength": 40,
+    "type": "string"
+  },
+  "maxItems": 4,
+  "type": "array"
+}

addedInput schema / properties / gdpr_dpa
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / hosting_provider

Added value: +{
+  "maxLength": 60,
+  "type": "string"
+}

addedInput schema / properties / launch_hook

Added value: +{
+  "maxLength": 140,
+  "type": "string"
+}

addedInput schema / properties / mcp_auth

Added value: +{
+  "items": {
+    "enum": [
+      "oauth",
+      "api"
+    ],
+    "type": "string"
+  },
+  "maxItems": 2,
+  "type": "array"
+}

addedInput schema / properties / mcp_docs_url

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / mcp_server_url

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / model_source

Added value: +{
+  "enum": [
+    "own",
+    "open-weight",
+    "provider",
+    "mixed",
+    "none"
+  ],
+  "type": "string"
+}

addedInput schema / properties / pricing_detail

Added value: +{
+  "maxLength": 400,
+  "type": "string"
+}

addedInput schema / properties / trains_on_customer_data

Added value: +{
+  "enum": [
+    "no",
+    "opt-out",
+    "yes"
+  ],
+  "type": "string"
+}

addedInput schema / properties / x_handle

Added value: +{
+  "maxLength": 40,
+  "type": "string"
+}

Changed1 schema field changedSep 12, 2026

addedInput schema / properties / logo_url

Added value: +{
+  "description": "New logo. Public https URL of the company logo: PNG, JPEG, WebP, GIF or AVIF, at least 64 px, max 5 MB. A square icon works best. Tulimoa downloads it, scales it to max 512 px and stores it as WebP. Required if the listing has no logo yet.",
+  "format": "uri",
+  "type": "string"
+}

Changed2 schema fields changedJul 28, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Listing id.",
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "status": {
+      "const": "pending",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "slug",
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 6, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "sales-crm",
-  "marketing",
-  "communication",
-  "productivity",
-  "developer-tools",
-  "finance-ops",
-  "hr-people",
-  "customer-support",
-  "data-analytics",
-  "ai-infra",
-  "compliance-hosting"
-]New value: +[
+  "developer-tools",
+  "ai-infra",
+  "sales-crm",
+  "marketing",
+  "productivity",
+  "data-analytics",
+  "finance-accounting",
+  "customer-support",
+  "hr-recruiting",
+  "design-creative",
+  "security-privacy",
+  "communication",
+  "commerce-payments",
+  "automation-nocode",
+  "other"
+]

AddedJun 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the review side effect (any edit resets status to pending and the listing disappears publicly until re-approved), the auth requirement (write-scoped login), and the logo precondition. It does not state whether omitted fields are preserved (partial vs. full replace), which is the one meaningful behavioral gap.

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?

Four tight sentences, front-loaded with the core action and key by slug, then the consequences and requirements. No filler, though the logo sentence duplicates schema text and could be trimmed.

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

Completeness3/5

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

For a 24-parameter mutation with low schema coverage, the description covers the important behavioral risks (review reset, auth, logo requirement) but leaves the bulk of the parameter surface unexplained. Output schema exists, so return values need not be described, which keeps this at an adequate rather than deficient level.

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 17% across 24 parameters, so the description needs to compensate and largely does not. It restates the slug and logo_url rules already present in the schema and adds the ownership/review constraints, but says nothing about the other ~20 fields (ai_usage, category, pricing_model, etc.).

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 ('Update fields of a listing you own (by slug)') and scopes it to owned listings, which cleanly separates it from submit_listing (create), get_listing (read), and search_listings. The identification key (slug) is named up front.

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?

Gives clear context for use: you must own the listing, you cannot change ownership or review status, and a write-scoped login is required. It does not explicitly name sibling tools as alternatives (e.g. use submit_listing for a new listing), so it falls short of a full 5.

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

All Tulimoa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.