> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-mcp/tool-reference/evaluations-and-monitoring/evals-dataset-rows-add.md).

# evals\_dataset\_rows\_add

Add test cases to an existing dataset.

**Effect:** This call saves data or changes configuration. Review the behavior below before using it.

## Inputs

| Name         | Type          | Requirement | Description                                                                                                                                         |
| ------------ | ------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `dataset_id` | string        | Required    | Dataset ID returned by dataset discovery or creation.                                                                                               |
| `rows`       | array of rows | Required    | At most 100 rows per call. Each has an `inputs` object and optional `expected_output` object and `source_run_id` UUID. The array must not be empty. |

Each row contains `inputs` (object), optional `expected_output` (object), and optional `source_run_id` (UUID string). Row input keys must match the dataset contract.

## Example

These are MCP tool arguments, not an HTTP request body. Replace bracketed IDs with values returned from your account.

This example assumes a Start input named `question` and an output named `out-0`. Replace them with the project’s actual keys. The regular-expression rule, where used, checks only that the output contains non-whitespace text.

```json
{
  "dataset_id": "<dataset-id>",
  "rows": [
    {
      "inputs": {
        "question": "What is the approval process?"
      }
    }
  ]
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "rows": [
    {
      "dataset_row_id": "<row-id>",
      "inputs": {
        "question": "What is the approval process?"
      }
    }
  ]
}
```

## Behavior

Adds at most 100 rows.

This append is not idempotent; inspect existing rows after an uncertain result before retrying.

## Troubleshooting

Each successful call appends rows. On a timeout, inspect all existing rows before adding anything again.

## Related resources

[Evaluations and monitoring](https://docs.stackai.com/stackai-mcp/tool-reference/evaluations-and-monitoring.md)

[Connection, permissions, pagination, and recovery](https://docs.stackai.com/stackai-mcp/best-practices-and-troubleshooting.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-mcp/tool-reference/evaluations-and-monitoring/evals-dataset-rows-add.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
