Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Pull competitor ads

pull_competitor_ads
Read-only

Retrieve a named brand's current live Meta (Facebook/Instagram) ads from the ad library, deduped and sorted, with correct page resolved. Just provide the brand or domain to see what they're running.

Instructions

THE FAST PATH for "show me the ads is running" — one named brand’s real live ads from the META (Facebook/Instagram) ad library, deduped, sorted, with the right page resolved. A single call, back in a few seconds. Prefer this over research_ads whenever the brand is named. Meta only, deliberately: it has by far the richest creative and is what people mean by "their ads". For Google or LinkedIn specifically, use search_google_ads or search_linkedin_ads. Spends credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo'longest_running' (default) etc.
limitNomax ads per platform (default 30)
domainNothe advertiser domain
countryNo2-letter, default 'US'
companyNameNothe advertiser name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.161
    • removedInput schema / properties / platforms
      Removed value: -{
-  "description": "default ['facebook']; add 'google','linkedin'",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "facebook": {
-      "description": "Meta results ({ads[], matched} or {error}; null when not requested)"
-    },
-    "google": {
-      "description": "Google results ({ads[], cursor} or {error}; null when not requested)"
-    },
-    "linkedin": {
-      "description": "LinkedIn results ({ads[], cursor} or {error}; null when not requested)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already mark this as read-only and non-destructive, and the description adds meaningful behavioral context: the call spends credits, returns deduped and sorted results, and resolves the correct page. This goes beyond the structured safety hints without contradicting them.

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 longer than the minimum but every sentence earns its place: it states the use case, scope, alternatives, and credit cost. The opening phrase is front-loaded and scannable, though the tone is slightly promotional.

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?

With no output schema, the description still communicates what the agent should expect conceptually: real live ads, deduped, sorted, and with the page resolved. It also covers scope, alternatives, and side effects, leaving only fine-grained return-field details unspecified.

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?

Schema description coverage is 100%, so the heavy lifting is done by the input schema. The description reinforces that the tool targets a 'named brand' and mentions sorting, but it does not add substantial parameter-level meaning beyond what the schema already provides.

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 opens with a clear, specific statement: it is the fast path for showing one named brand's real live ads from the Meta ad library, deduped, sorted, and with the right page resolved. It names concrete alternatives like research_ads and search_google_ads, making the tool's niche unmistakable.

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

Usage Guidelines5/5

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

The description explicitly says to prefer this tool over research_ads whenever the brand is named, and directs users to search_google_ads or search_linkedin_ads for Google or LinkedIn. This gives an agent clear routing rules with no need for inference.

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