Connect Google Sheets to Datadog

Add a single row of data to Google Sheets. Optionally insert the row at a specific index (e.g., row 2 to insert after headers, shifting existing data down). See the documentation

Add multiple rows of data to a Google Sheet. See the documentation

Get all values or values from a range of cells using A1 notation. See the documentation

Create conditional formatting with color scales or custom formulas. See the documentation

Add edit protection to cell range with permissions. See the documentation

Append one or more rows to a Google Sheets worksheet. Pass rows as a JSON array. **Preferred format:** array of objects with column header keys (e.g., [{"Name": "Alice", "Email": "alice@example.com"}]). Use **Get Spreadsheet Info** first to discover the exact column header names — keys must match headers exactly (case-sensitive). Alternatively, pass rows as arrays of positional values matching column order. New rows are appended after the last row with data.

Add a new worksheet (tab) to an existing spreadsheet. Optionally set column headers. Use **Get Spreadsheet Info** to see existing worksheets before creating.

Delete the content of a specific cell in a spreadsheet. See the documentation

Delete the content of a row or rows in a spreadsheet. Deleted rows will appear as blank rows. See the documentation

Copy an existing worksheet to another Google Sheets file. See the documentation

Create a new column in a spreadsheet. See the documentation

Create a blank spreadsheet or duplicate an existing spreadsheet. See the documentation

Create a blank worksheet with a title. See the documentation

Remove conditional formatting rule by index. See the documentation

Deletes the specified rows from a spreadsheet. See the documentation

Delete a specific worksheet. See the documentation

Find one or more rows by a column and value. See the documentation

Search for rows matching a value in a specific column. Use **Get Spreadsheet Info** to discover column header names. Returns matching rows as objects with row numbers (useful for subsequent **Update Rows** calls). For simple reads without filtering, use **Read Rows** instead.

Fetch the contents of a specific cell in a spreadsheet. See the documentation

Retrieve Google Sheets account metadata for the authenticated user by calling Drive's about.get, returning the user profile (display name, email, permission ID) and storage quota information. Helpful when you need to verify which Google account is active, tailor sheet operations to available storage, or give an LLM clear context about the user identity before composing read/write actions. See the Drive API documentation.

Returns the spreadsheet at the given ID. See the documentation for more information

Get the structure of a Google Spreadsheet — worksheet names, column headers (first row of each sheet), and row counts. **Call this first** before reading or writing data, so you know the worksheet names and column headers. The column headers are used as keys when writing data with **Add Rows** or **Update Rows**. The spreadsheet ID is the long string in the Google Sheets URL: https://docs.google.com/spreadsheets/d/{spreadsheetId}/edit.

Insert a note on a spreadsheet cell. See the documentation

Insert a comment into a spreadsheet. See the documentation

Detect the Datadog region for the connected account. Call this FIRST before any other Datadog tool if you do not already know the region. Returns the region domain (e.g. datadoghq.com) which must be passed as the region parameter to **Search Logs**, **Search Monitors**, **Get Metric Data**, and all other Datadog tools. See the docs

Detect the Datadog region for the connected account by validating the API key against each regional endpoint. Use this to discover the correct region before calling other Datadog actions. See the docs

Query time-series metric data for analyzing trends and system performance. Query syntax: avg:system.cpu.user{*}, sum:requests.count{env:prod} by {host}, max:system.mem.used{service:web}. Both from and to are POSIX timestamps in seconds. Use **Search Metrics** first to discover available metric names. Use **Search Hosts** to find valid host tags for scoping. After finding anomalies, use **Search Logs** to investigate related entries. See the docs

Get a list of logs matching a filter query. Uses the GET endpoint with a higher rate limit (3600/hr vs 300/hr). See the docs

Post custom time-series metric data points to Datadog. Data appears in dashboards, monitors, and can be queried via **Get Metric Data**. Points: JSON object where keys are Unix timestamps (seconds) and values are numeric, e.g. {"1640995200": 1.0}. Use **Search Metrics** to verify a metric name exists, or post to a new name to create it. This is a WRITE operation that creates or appends data to a metric time series. See the docs

List and search Datadog dashboards. Returns dashboard IDs, titles, URLs, and metadata. Dashboard URL: https://app.{region}/dashboard/{id} where region comes from **Get Account Info**. Use alongside **Search Services** to find dashboards related to a specific service. See the docs

Search Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter by sources (e.g. nagios,docker), tags (e.g. env:prod,service:web), and priority (normal or low). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use **Search Monitors** first, then search events for the relevant time range. Follow up with **Search Logs** for deeper investigation. See the docs

Search monitored infrastructure hosts. Filter by tag (env:production), name (host:web-01), or partial match. Sort by cpu, iowait, load, status, or apps. Host names from results can scope queries in **Get Metric Data** (e.g. avg:system.cpu.user{host:web-01}), filter logs in **Search Logs** (host:web-01), or filter metrics in **Search Metrics**. Max 1000 results. See the docs

Search Datadog incidents by state, severity, and metadata. Query syntax: state:active, state:resolved, severity:SEV-1. After finding an incident, investigate with: **Search Logs** for the incident time window, **Get Metric Data** for relevant metrics, **Search Events** for related monitor alerts, and **Search Services** for ownership info. See the docs

Search Datadog logs matching a query with support for facets and time ranges. Uses log search syntax: service:web-app status:error, @http.status_code:>=400, boolean operators (AND, OR, NOT), and wildcards. Set from to now-1h for recent logs. Use **Search Metrics** to discover metric names or **Search Hosts** to find host names for filtering. To investigate an incident, use **Search Incidents** first, then search logs for that time window and service. See the docs

Discovery tool: list available Datadog metric names, optionally filtered by host. Returns metric name strings (e.g. system.cpu.user, aws.ec2.cpuutilization) for use in **Get Metric Data** queries with the syntax aggregation:metric.name{tags}. Use **Search Hosts** to find valid host names for the host filter. See the docs

Search Datadog monitors (alerting rules) including status, thresholds, and conditions. Query syntax: tag:env:production, type:metric, status:Alert. Tags filter: comma-separated (e.g. env:prod,team:backend). After finding a monitor, use **Search Events** to see recent state changes, or **Get Metric Data** to query the underlying metric it tracks. Returns monitor ID, name, type, query, status, and tags. See the docs

List services from Datadog's Service Catalog with ownership, metadata, and team info. Use to discover service names for filtering in **Search Logs** (service:my-app) or finding monitors via **Search Monitors** (tag:service:my-app). Returns service definitions including links, docs, and on-call. See the docs