Skip to main content
Glama

AIsa Sales

by one.aisa
OverviewDiscussionsAdmin

Get a List of Fields + Create a Custom Field

post_apollo_fields
Destructive

Get a list of fields. Requires a master API key.

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "label": {
+      "description": "Name of the custom field you want to create. Example: `Test Name`",
+      "type": "string"
+    },
+    "meta": {
+      "properties": {
+        "max_length": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "modality": {
+      "description": "The modality of the custom field you want to create.  Example: `contact`",
+      "enum": [
+        "contact",
+        "account",
+        "opportunity"
+      ],
+      "type": "string"
+    },
+    "type": {
+      "description": "What kind of custom field you want to create. Example: `textarea`",
+      "enum": [
+        "string",
+        "textarea",
+        "number",
+        "date",
+        "datetime",
+        "boolean"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / label
      Removed value: -{
-  "description": "Field label.",
-  "type": "string"
-}
    • removedInput schema / properties / meta
      Removed value: -{
-  "description": "Additional field config.",
-  "type": "object"
-}
    • removedInput schema / properties / modality
      Removed value: -{
-  "description": "Entity modality (e.g., contact).",
-  "type": "string"
-}
    • removedInput schema / properties / type
      Removed value: -{
-  "description": "Field type (e.g., textarea).",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "body"
+]
  2. First observed

TDQS

D1.7/5.0
Behavior1/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, but the description says only "Get a list of fields," implying a read. This contradicts the annotations and hides the destructive write nature. The only useful extra is the master API key requirement.

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

Conciseness2/5

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

The two real sentences are terse, but a large auto-generated pricing block occupies much of the text and conveys nothing about tool selection or behavior. The minimal information present is also front-loaded around the wrong (read) action.

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?

Although an output schema exists (so return values need not be described), the definition is incomplete for a destructive write tool: it never states it creates a custom field, never covers the required body parameters, and its stated action conflicts with the annotations.

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

Parameters1/5

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

Schema description coverage is 0% at the top level and the description mentions no parameters at all. It adds nothing about the nested body fields (type, label, modality, meta) that drive field creation.

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

Purpose2/5

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

The description only says "Get a list of fields," but the tool name (post_), the title ("Get a List of Fields + Create a Custom Field"), and the body schema with type/label/modality all indicate the primary action is creating a custom field. The description omits the create function entirely and is therefore partial/misleading about what the tool does.

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

Usage Guidelines2/5

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

No when-to-use, when-not, or alternative guidance is given. Siblings get_apollo_fields and get_apollo_typed_custom_fields appear to be the pure read routes, yet the description does not distinguish this mutating tool from them.

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

All AIsa Sales toolsInspect
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.

Resources