Skip to main content
Glama

AIsa Technologies & Whois

by one.aisa
OverviewDiscussionsAdmin

Technology Stats

post_dataforseo_domains_tech_technology_stats_live
Destructive

‌‌ The Technology Stats endpoint will provide you with historical data on the number of domains across different countries and languages that use the specified technology.

Usage-based billing; Default request estimate: $0.012 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / body / items / oneOf
      Previous value: -[
-  {
-    "example": [
-      {
-        "date_from": "2022-10-31",
-        "date_to": "2023-06-01",
-        "technology": "jQuery"
-      }
-    ],
-    "properties": {
-      "date_from": {
-        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "date_to": {
-        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "tag": {
-        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "technology": {
-        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "technology": {
+        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "date_from": "2022-10-31",
-        "date_to": "2023-06-01",
-        "technology": "jQuery"
-      }
-    ],
-    "properties": {
-      "date_from": {
-        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "date_to": {
-        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "tag": {
-        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "technology": {
-        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / oneOf
      Added value: +[
+  {
+    "example": [
+      {
+        "date_from": "2022-10-31",
+        "date_to": "2023-06-01",
+        "technology": "jQuery"
+      }
+    ],
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "technology": {
+        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
+  {
+    "date_from": "2022-10-31",
+    "date_to": "2023-06-01",
+    "technology": "jQuery"
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "date_from": "2022-10-31",
+        "date_to": "2023-06-01",
+        "technology": "jQuery"
+      }
+    ],
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "technology": {
+        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / properties
      Removed value: -{
-  "date_from": {
-    "description": "starting date of the time range optional field minimum value: 2022-10-31 if you don’t specify this field, the minimum value will be used by default date format: \"yyyy-mm-dd\" example: \"2023-06-01\"",
-    "type": "string"
-  },
-  "date_to": {
-    "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default date format: \"yyyy-mm-dd\" example: \"2023-01-15\"",
-    "type": "string"
-  },
-  "tag": {
-    "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response",
-    "type": "string"
-  },
-  "technology": {
-    "description": "target technology required field you can find the full list of technologies you can specify here on this page example: \"Salesforce\"",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "technology"
-]
    • changedInput schema / properties / body / items / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "body"
-]New value: +[]
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed7 schema fields changed
    • removedInput schema / properties / body / example
      Removed value: -[
-  {
-    "date_from": "2022-10-31",
-    "date_to": "2023-06-01",
-    "technology": "jQuery"
-  }
-]
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "date_from": "2022-10-31",
-        "date_to": "2023-06-01",
-        "technology": "jQuery"
-      }
-    ],
-    "properties": {
-      "date_from": {
-        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "date_to": {
-        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "tag": {
-        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "technology": {
-        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / properties
      Added value: +{
+  "date_from": {
+    "description": "starting date of the time range optional field minimum value: 2022-10-31 if you don’t specify this field, the minimum value will be used by default date format: \"yyyy-mm-dd\" example: \"2023-06-01\"",
+    "type": "string"
+  },
+  "date_to": {
+    "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default date format: \"yyyy-mm-dd\" example: \"2023-01-15\"",
+    "type": "string"
+  },
+  "tag": {
+    "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response",
+    "type": "string"
+  },
+  "technology": {
+    "description": "target technology required field you can find the full list of technologies you can specify here on this page example: \"Salesforce\"",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / items / required
      Added value: +[
+  "technology"
+]
    • changedInput schema / properties / body / items / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +"object"
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "body"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  5. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
+  {
+    "date_from": "2022-10-31",
+    "date_to": "2023-06-01",
+    "technology": "jQuery"
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "date_from": "2022-10-31",
+        "date_to": "2023-06-01",
+        "technology": "jQuery"
+      }
+    ],
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>minimum value: <code>2022-10-31</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-06-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2023-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "technology": {
+        "description": "<em>target technology</em><br><strong>required field</strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br>example:<br><code>\"Salesforce\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / properties
      Removed value: -{
-  "date_from": {
-    "description": "starting date of the time range optional field minimum value: 2022-10-31 if you don’t specify this field, the minimum value will be used by default date format: \"yyyy-mm-dd\" example: \"2023-06-01\"",
-    "type": "string"
-  },
-  "date_to": {
-    "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default date format: \"yyyy-mm-dd\" example: \"2023-01-15\"",
-    "type": "string"
-  },
-  "tag": {
-    "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response",
-    "type": "string"
-  },
-  "technology": {
-    "description": "target technology required field you can find the full list of technologies you can specify here on this page example: \"Salesforce\"",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "technology"
-]
    • changedInput schema / properties / body / items / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "body"
-]New value: +[]
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  6. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The description frames the endpoint purely as a data retrieval ('will provide you with historical data'), while annotations declare readOnlyHint=false and destructiveHint=true. That is the same read-versus-destructive mismatch flagged in the calibration for annotation contradictions. The only genuine added context is the pricing note, which does not offset the contradiction.

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?

Core purpose is a single front-loaded sentence, with pricing clearly separated into its own block. A stray leading zero-width character and the billing clamp add minor noise, but nothing is bloated.

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?

An output schema exists, so return values needn't be described. However, for a POST data endpoint sitting among five overlapping tech siblings, the description supplies no selection criteria, no date-range defaults, and no note that 'technology' is mandatory inside the body array - gaps the schema alone does not close.

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 top-level 'body' wrapper has no description (0% coverage on the reported metric) and the description adds no parameter information at all. The nested properties (tag, date_to, date_from, technology) do carry rich inline descriptions with formats, defaults, and examples, so the effective gap is narrower than the metric suggests, but the description itself contributes nothing.

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 resource and output: historical domain counts by country/language for a specified technology. That is far more informative than the bare title 'Technology Stats'. It does not, however, differentiate itself from closely named siblings like post_dataforseo_domains_tech_aggregation_live, summary_live, or domains_by_technology_live, which an agent would have to disambiguate on its own.

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?

The description never says when to prefer this endpoint over the sibling tech endpoints (aggregation, summary, domains_by_technology) that clearly overlap. There is also no mention of defaults for the date range or that a technology must be supplied, despite the schema requiring it inside the body object.

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

All AIsa Technologies & Whois toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources