# google_ads_search_terms_analyze

Analyze keyword/search-term overlap and N-gram distribution

Agent View of the PolicyLayer registry record for `google_ads_search_terms_analyze`. HTML page: https://policylayer.com/tools/logly-mureo/google-ads-search-terms-analyze

## Facts

- Tool: `google_ads_search_terms_analyze`
- Server: Mureo (`logly/mureo`) — https://policylayer.com/tools/logly-mureo.md
- Homepage: https://github.com/logly/mureo
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "google_ads_search_terms_analyze",
    "arguments": {}
  }
}
```

## Why google_ads_search_terms_analyze is rated Low

This tool retrieves and analyzes existing search term data from Google Ads accounts to provide insights on keyword overlap and distribution patterns. It performs statistical analysis on data without creating, modifying, deleting resources, or executing arbitrary code. The operation is read-only with no side effects on the advertising system.

From the tool's own definition: "Tool name and description indicate analysis and reporting functions: 'Analyze keyword/search-term overlap and N-gram distribution'. These are query and aggregation operations with no modification, deletion, or execution of external code."

## Use case

AI agents call google_ads_search_terms_analyze to retrieve information from Mureo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mureo:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_ads_search_terms_analyze": {}
  }
}
```

## Other tools on Mureo (224)

- `google_ads_callouts_remove` — Destructive — https://policylayer.com/tools/logly-mureo/google-ads-callouts-remove.md
- `google_ads_conversions_remove` — Destructive — https://policylayer.com/tools/logly-mureo/google-ads-conversions-remove.md
- `google_ads_keywords_remove` — Destructive — https://policylayer.com/tools/logly-mureo/google-ads-keywords-remove.md
- `google_ads_negative_keywords_remove` — Destructive — https://policylayer.com/tools/logly-mureo/google-ads-negative-keywords-remove.md
- `google_ads_negative_placements_remove` — Destructive — https://policylayer.com/tools/logly-mureo/google-ads-negative-placements-remove.md
- `google_ads_sitelinks_remove` — Destructive — https://policylayer.com/tools/logly-mureo/google-ads-sitelinks-remove.md
- `meta_ads_ad_rules_delete` — Destructive — https://policylayer.com/tools/logly-mureo/meta-ads-ad-rules-delete.md
- `meta_ads_audiences_delete` — Destructive — https://policylayer.com/tools/logly-mureo/meta-ads-audiences-delete.md
- `meta_ads_catalogs_delete` — Destructive — https://policylayer.com/tools/logly-mureo/meta-ads-catalogs-delete.md
- `meta_ads_products_delete` — Destructive — https://policylayer.com/tools/logly-mureo/meta-ads-products-delete.md
- `meta_ads_split_tests_end` — Destructive — https://policylayer.com/tools/logly-mureo/meta-ads-split-tests-end.md
- `rollback_apply` — Destructive — https://policylayer.com/tools/logly-mureo/rollback-apply.md
- `google_ads_btob_optimizations` — Execute — https://policylayer.com/tools/logly-mureo/google-ads-btob-optimizations.md
- `google_ads_capture_screenshot` — Execute — https://policylayer.com/tools/logly-mureo/google-ads-capture-screenshot.md
- `meta_ads_conversions_send` — Execute — https://policylayer.com/tools/logly-mureo/meta-ads-conversions-send.md
- `meta_ads_conversions_send_purchase` — Execute — https://policylayer.com/tools/logly-mureo/meta-ads-conversions-send-purchase.md
- `mureo_analytics_run` — Execute — https://policylayer.com/tools/logly-mureo/mureo-analytics-run.md
- `google_ads_budget_reallocation` — Financial — https://policylayer.com/tools/logly-mureo/google-ads-budget-reallocation.md
- `meta_ads_instagram_boost` — Financial — https://policylayer.com/tools/logly-mureo/meta-ads-instagram-boost.md
- `meta_ads_page_posts_boost` — Financial — https://policylayer.com/tools/logly-mureo/meta-ads-page-posts-boost.md
- `analysis_anomalies_check` — Read — https://policylayer.com/tools/logly-mureo/analysis-anomalies-check.md
- `analysis_delivery_collapse_check` — Read — https://policylayer.com/tools/logly-mureo/analysis-delivery-collapse-check.md
- `analysis_delivery_collapse_diagnose` — Read — https://policylayer.com/tools/logly-mureo/analysis-delivery-collapse-diagnose.md
- `analysis_exclusion_impact_preview` — Read — https://policylayer.com/tools/logly-mureo/analysis-exclusion-impact-preview.md
- `analysis_tracking_consistency_check` — Read — https://policylayer.com/tools/logly-mureo/analysis-tracking-consistency-check.md
- `creative_studio_brand_kit_get` — Read — https://policylayer.com/tools/logly-mureo/creative-studio-brand-kit-get.md
- `creative_studio_providers_list` — Read — https://policylayer.com/tools/logly-mureo/creative-studio-providers-list.md
- `google_ads_accounts_list` — Read — https://policylayer.com/tools/logly-mureo/google-ads-accounts-list.md
- `google_ads_ad_groups_list` — Read — https://policylayer.com/tools/logly-mureo/google-ads-ad-groups-list.md
- `google_ads_ad_performance_compare` — Read — https://policylayer.com/tools/logly-mureo/google-ads-ad-performance-compare.md
- …and 194 more: https://policylayer.com/tools/logly-mureo.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=logly-mureo · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/logly-mureo