diff --git a/mcp-server.mdx b/mcp-server.mdx
index 26feac1..1b22d2d 100644
--- a/mcp-server.mdx
+++ b/mcp-server.mdx
@@ -284,6 +284,10 @@ validation, routing, failover, pricing, and billing are identical.
 
     For long-running work, `run_api` waits briefly, then returns a Request ID with a
     `nextAction`. Call `get_request` instead of repeating `run_api`.
+
+    `linkedin.ads_search` may also return a `date_adjusted:` hint with the dates used
+    for your search. These dates remain unchanged on replay. See
+    [LinkedIn ad date filters](/quickstart#linkedin-ad-date-filters).
   </Accordion>
   <Accordion title="get_request - resume durable work" icon="clock">
     Retrieve a durable Request by ID. It never repeats the paid operation.
diff --git a/quickstart.mdx b/quickstart.mdx
index 014eb7a..ccd681a 100644
--- a/quickstart.mdx
+++ b/quickstart.mdx
@@ -121,6 +121,17 @@ yourself, follow the steps below.
   </Step>
 </Steps>
 
+## LinkedIn ad date filters
+
+For `linkedin.ads_search`, LinkedIn accepts `startDate` and `endDate` from one year ago
+through yesterday in UTC. If your date range overlaps that window, AnyAPI moves an earlier
+start date forward and moves today or a later end date back to yesterday. The response's
+optional `hint` starts with `date_adjusted:` and names the adjusted dates used for your search.
+The dates stay the same if the response arrives after midnight or you replay the request.
+
+A reversed range or a range with no accepted day is rejected before the search. You are not
+charged for that rejection.
+
 ## Find an API
 
 To browse by eye, start at [the full catalog](https://getanyapi.com/catalog) or a