Skip to main content
Glama
studiomeyer-io

meetmyagent-mcp

by studiomeyer-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mma_get_listing

Fetch a single marketplace listing by ID to retrieve its full details, including agent information and verified-business badge, along with next-action links.

Instructions

Fetch one listing by id — full detail incl. the agent/provider behind it, the verified-business badge, and next-action links. The human-readable page is https://meetmyagent.io/en/listings/{id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNoNext-action links — chain by following `rel`, never by rebuilding URLs.
listingYesA public listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "links": {
+      "description": "Next-action links — chain by following `rel`, never by rebuilding URLs.",
+      "items": {
+        "properties": {
+          "href": {
+            "type": "string"
+          },
+          "method": {
+            "type": "string"
+          },
+          "rel": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "rel",
+          "method",
+          "href"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "listing": {
+      "description": "A public listing.",
+      "properties": {
+        "aiVisibilityScore": {
+          "type": "number"
+        },
+        "attributes": {
+          "type": "object"
+        },
+        "boosted": {
+          "type": "boolean"
+        },
+        "category": {
+          "type": "string"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "description": {
+          "type": "string"
+        },
+        "domainVerified": {
+          "type": "boolean"
+        },
+        "id": {
+          "type": "string"
+        },
+        "location": {
+          "type": "object"
+        },
+        "media": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "priceCents": {
+          "type": "number"
+        },
+        "provider": {
+          "type": "object"
+        },
+        "ratingAvg": {
+          "type": "number"
+        },
+        "ratingCount": {
+          "type": "number"
+        },
+        "status": {
+          "enum": [
+            "draft",
+            "active",
+            "paused",
+            "archived"
+          ],
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "category",
+        "title",
+        "description",
+        "status"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "listing"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

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 burden of communicating behavior. It makes clear this is a read-style 'fetch' that returns a single listing's full detail, including agent/provider and follow-up links. It does not discuss auth, rate limits, or failure behavior, but for a simple one-item get operation it is reasonably transparent.

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?

The description is compact, front-loaded with the main action, and scannable. The human-readable page URL adds extra context but is not essential for API usage, keeping it from a perfect conciseness score.

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?

For a single-parameter read tool, the description covers purpose, result scope, notable included fields, and even provides a related human-facing resource. With an output schema present, it does not need to enumerate every return field, so this is a complete enough description for selection and invocation in most cases.

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?

The schema only defines one required string 'id' with no per-parameter description, so the phrase 'by id' provides the essential mapping from the parameter to the listing identity. However, it does not clarify id format, whether it is an internal id only, or how to obtain it beyond the human-readable URL hint. This is adequate but not value-adding beyond the schema.

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 states a specific action ('Fetch one listing by id'), a clear resource ('listing'), and a meaningful scope ('full detail') that distinguishes it from broader or sibling tools. It also names the included entities (agent/provider, verified-business badge, links), making the tool's purpose concrete.

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?

The description implies the right context—when you have a listing id and need full listing details—but it does not explicitly mention when not to use it or point to sibling alternatives like mma_search or mma_get_provider. The usage signal is clear but not fully spelled out.

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

Deploy Server

Other Tools